On Sun, 2005-12-04 at 15:54 -0800, ceejay wrote:
> First, the database as it is... has many tables!
All useful relational databases have lots of tables.
Having lots of relationships is why the 6.* series
went to the database.
> This means that code along the lines I was thinking of, allowing the
> user to do queries on different roles, can be done without any changes
> to the database (I think).
An admirable goal. Adding queries is fairly safe.
Altho the database schema is a little bit of a moving target
right now.
> I suspect your completely general approach to using any tag in any way
> you like just might be a step too far.
Most likely.
> Ideally I suppose you'd like to enter partial searches on each of
> several different tags.
Right, both predefined as part of the standard release,
and then whatever folks need for the way their library is
implemented.
> BTW, keeping the Album title really short ("Symphony 1") won't work -
> it MUST contain enough information to make it unique vs all other
> albums, otherwise Slimserver (and other music players) will merge the
> tracks of the ambiguous albums.
It should not do this. Using the name is bad design.
Each tune/song should be identified not by its tags, but by
the music itself. Tags are just comments for us humans.
--
Pat
http://www.pfarrell.com/music/slimserver/slimsoftware.html
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
