If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > MySQL > Music Store Database

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-21-04, 12:33
jcdouville jcdouville is offline
Registered User
 
Join Date: Apr 2004
Posts: 1
Question Music Store Database

Hi All,

I am starting an online music store and am learning MySQL from the ground up. I have a few questions...

Is MySQL sufficient for large online music stores? (Do you think iTunes or Walmart would use it?)

I have different tables for objects such as albums, songs, artists, etc... but it seems that the songs table is going to get very large very soon, should I break that one up?

I have an artist_id for each song and album, is there some way I can not use it for album, but some how get the artist_id from the song when viewing it's album?

Thanks Alot!
Reply With Quote
  #2 (permalink)  
Old 04-22-04, 06:52
hurmavi hurmavi is offline
Registered User
 
Join Date: Jan 2004
Location: Europe, Finland, Helsinki
Posts: 60
Re: Music Store Database

Quote:
Originally posted by jcdouville
Hi All,

I am starting an online music store and am learning MySQL from the ground up. I have a few questions...

Is MySQL sufficient for large online music stores? (Do you think iTunes or Walmart would use it?)

I have different tables for objects such as albums, songs, artists, etc... but it seems that the songs table is going to get very large very soon, should I break that one up?

I have an artist_id for each song and album, is there some way I can not use it for album, but some how get the artist_id from the song when viewing it's album?

Thanks Alot!
Yes indeed!

<Sufficient for large online...>
MySQL is indeed large enough for music store. Have a faith!

<...should I break that one...>
Don't anticipate things like that. Again, have a faith. If you have later some problems, act anly then!


Cheers, Bill
Reply With Quote
  #3 (permalink)  
Old 04-27-04, 12:38
snorp snorp is offline
Registered User
 
Join Date: Apr 2004
Location: Europe->Sweden->Stockholm
Posts: 71
If I was to use MySQL I would probably use InnoDB instead of MyISAM at least. Even if you have UPS and backup power to keep everything running at all times, it's pretty neat to be able to ROLLBACK when you've forgot that "AND id=12345" in your DELETE FROM and saw "654321 rows affected"

Very well, when it comes to the stability of MySQL I have managed to get crashed MyISAM tables when testing some alpha version a few years ago. (It took 48+ hours to do an REPAIR TABLE ... EXTENDED, and the table crashed again soon.)

However, I have never managed to break something with a stable version or with 5.0.0-alpha.

Don't forget the backups, of course...
Reply With Quote
  #4 (permalink)  
Old 06-26-10, 00:11
lagon22 lagon22 is offline
Registered User
 
Join Date: Jun 2010
Posts: 1
Quote:
Originally Posted by snorp View Post
Even if you have UPS and backup power to keep everything running at all times, it's pretty neat to be able to ROLLBACK when you've forgot that "AND id=12345" in your DELETE FROM and saw "654321 rows affected"
That is so hilarious and mind-FRIGGIN! I can never imagine that happening. The only way to buy back everything is by selling your soul to the devil LOL!
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On