INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC11 - How does the Relational DB work?  (Read 1614 times)

EpF

  • Citizen of the Universe
  • *****
  • Posts: 649
MC11 - How does the Relational DB work?
« on: July 26, 2004, 04:50:54 pm »

I was wondering if the new relational system in MC11 means that I can make an 'Artist Rating' field and then once I fill in a rating for an artist, all files with that artist in the tag automatically shows up the same rating?  That'd be SOOO cool!

 ;D

Listening to: Underworld - 'Spoon Deep', from 'Dark & Long'

TAFKAFEX

  • Guest
Re:MC11 - How does the Relational DB work?
« Reply #1 on: July 26, 2004, 05:15:37 pm »

Your question could lead to a minefield.

Example: There are some artists who change their 'Genre' over the years. So if you chang the 'Genre' for this artist, you want to change all 'Genre' for all his older albums? Or the newer ones? Or all of his tracks?

Where is the border?

Listening to: 'Let's All Make A Bomb' from 'How Live Is' by 'Heaven 17' on Media Center 11
Logged

IanG

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 528
Re:MC11 - How does the Relational DB work?
« Reply #2 on: July 26, 2004, 05:42:09 pm »

I was wondering if the new relational system in MC11 means that I can make an 'Artist Rating' field and then once I fill in a rating for an artist, all files with that artist in the tag automatically shows up the same rating?  That'd be SOOO cool!

It's technicaly possible, but there would have to be some way for the user to  define the relationship between the 2 fields.  It would be nice to have, but it's probably not worth the trouble.

Ian G.
Logged

EpF

  • Citizen of the Universe
  • *****
  • Posts: 649
Re:MC11 - How does the Relational DB work?
« Reply #3 on: July 26, 2004, 05:53:00 pm »

Your question could lead to a minefield.

TafkaFex  - Point taken, but in fairness it would only be a minefield of people's own individual making!  I mean, if I don't make a custom 'artist genre' field, then I don't have that problem...  

Your point is more related to the issue of genres in general than to the use of 'group' fields, for want of a better term.


It's technicaly possible, but there would have to be some way for the user to  define the relationship between the 2 fields.  It would be nice to have, but it's probably not worth the trouble.

Ian G.

Ian - fair enough, but can you tell me what effect a relational database has on organising the MC library?  That's really what I was trying to find out...

kaiynne

  • Regular Member
  • World Citizen
  • ***
  • Posts: 225
  • I Changed this by choosing profile
Re:MC11 - How does the Relational DB work?
« Reply #4 on: July 27, 2004, 02:01:42 am »

Not sure if this will be enabled in MC11 but could certainly perform this operation within a relational database quite easily.

firstly create a user defined field called album rating and force all tracks under that album to have the same album rating.  I do this in Mc10, but obviously have to select all tracks from the album and tag them at once.  Doesn't take much longer than it would were this enabled though.  But there may be other uses which would benefit from such database manipulation power.
Logged

IanG

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 528
Re:MC11 - How does the Relational DB work?
« Reply #5 on: July 27, 2004, 03:31:44 am »



It's technicaly possible, but there would have to be some way for the user to  define the relationship between the 2 fields.  It would be nice to have, but it's probably not worth the trouble.

Ian G.

Ian - fair enough, but can you tell me what effect a relational database has on organising the MC library?  That's really what I was trying to find out...

Assuming there's no facility for managing relationships, I don't think it'll have any effect.  Let's use your example of an artist rating.  I'd expect MC to have a table of artists - each artist will have a name and an ID.  When you tag a file in the db, it's the ID that goes against the file, not the name.  Suppose I now decide that "Yngwie Malmsteen" should be "Yngwie J Malmsteen", the name in the artist table gets changed, but nothing else since the files are associated with the name via the ID, and that didn't change - it's quick and efficient.  

Suppose you now want to add your artist rating field - the normal way would be to add another field to the artist table.  There's no tool to do that, so you have to create the field, manualy select all the Yngwie tracks and then update the artist rating field for each one.  Not much of a task, but you'll have to do it each time you add a new track.

I guess MC could include a db management tool but, as TafkaFex has already said, it's a minefield! I think this a case where simplicity is more important than efficiency.

Ian G.
Logged
Pages: [1]   Go Up