On 6/1/05, Martijn Voncken <[EMAIL PROTECTED]> wrote: > I'm willing to change to a design with EMPTY hybrid tables. > *It will really speed up initial development. (compared to full hybrid > right away) > *common api's will remain the same. > *if testing/application requires more performance,a switch to hybrid > is still possible.
Hi, The current (still changing) sqlite schema i'm experimenting with. A full attr,value schema without hybrid tables. create table attr (attrid integer primary key,attrname character) insert into attr values (1,'dirpath') insert into attr values (2,'dirtitle') create table media (mediaid integer primary key,medianame character) insert into media values (0,'audio') insert into media values (1,'video') insert into media values (2,'image') insert into media values (3,'misc') create table file (fileid integer primary key ,mediaid integer,path character,mtime integer) create index ix_file_path on file (path) create table file_attr (fileid integer ,mediaid integer,attrid integer,value character) create unique index ix_file_attr on file_attr (fileid,attrid) create index ix_file_attr_media_val on file_attr (mediaid,attrid,value) --- I chose integer-id/indexes because they perform better on most databases. Optimized for current media-db use +searching on attribute-value per media. I have still to design/decide what to do with directory's -i need at least an mtime per dir. -perhaps even a 1'st class table for directory's -directory's need attributes too. -leaning towards insert into media values (5,'dir') Martijn. ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel