database - Should I use one table if derived tables would all use the same record layout? -
i'm developing game sdk, centers on establishment , persistence of storyline, characters, leveling, etc.
i started mindmap of different classes, , in process of bringing simple representations uml. since persisting of game's objects done using sqlite, representing classes database record types. 1 of record types, rangedproperty, used in multiple tables: factions, traits, statuses, etc.
create table [rangedproperty] ( [uid] integer not null on conflict fail, [oid] integer not null, [name] text, [description] text, [tag] text, [min] integer default 1, [max] integer default 100, [current] integer default 50);
since tables using same record type, make sense leave tag field in place, , - rather using separate tables factions, traits, , on - use same table them all? seems contribute reliability, since changes record type need made 1 table, reducing likelihood of error.
thanks!
note: have thought of using integer field type, since make faster comparisons, consider moot point if tag field isn't used.
Comments
Post a Comment