From: Christopher O. <oe...@oe...> - 2007-08-29 07:46:48
|
> With that said, I expect the scheme to be something like this: > > --------------------------------------------------- > TABLE: entries > col1: ID (uniquely identifies the entry. same in all tables) > col2: type (indicates which entry type table the details are stored in) > > TABLE: article > col1: ID > col2: title > col3: journal > : > : > colN: date published (or something similar) > > TABLE: book > col1: ID > col2: title > etc... > > (and so on for each entry type including user-defined) > > TABLE: groups > col1: ID > col2: group1 > col2: group2 > etc... I am not a database expert but I would suggest the following: TABLE entries col1: ID col2: type (is a string) col3: author col4: editor col5: title ... ... All the required and optional fields (you can look these up from JabRef) ... TABLE customFields col1: ID (as a foreign key into entries table) col2: fieldName (for instance for holding ISBN) col3: fieldValue It is of course possible with the dynamical approach to put the customFields into the entries table as well. TABLE groups col1: ID (as a foreign key into entries table) col2: group (as a string label for the group) Technically the groups solution is not very clean, as you should not have duplicate group values (but rather IDs into a groupType table). Cheers, Christopher |