Re: [GENERAL] New DB-design - help and documentation pointers appreciated

2010-07-20 Thread Craig Ringer
On 20/07/10 18:14, Rikard Bosnjakovic wrote: > However, I feel that this design is the same design I seem to use for > all my databases, and in the end I always find that I designed them > wrong from the beginning. The table "components" feels like that one > is going to be locked into a corner; i

Re: [GENERAL] New DB-design - help and documentation pointers appreciated

2010-07-20 Thread Rikard Bosnjakovic
On Sat, Jul 3, 2010 at 03:51, Craig Ringer wrote: [...] > You've hit one of those areas where SQL databases kind of suck. You'll > have to use one of the well understood workarounds like EAV and live > with their limitations, or find a database better suited to the data. Thanks for the feedback

Re: [GENERAL] New DB-design - help and documentation pointers appreciated

2010-07-02 Thread Craig Ringer
On 03/07/10 02:43, Rikard Bosnjakovic wrote: > However, the table that really makes me cringe in fear of un-knowledge > is this one: parameters. A parameter for a component can be something > that tells the designer that it must exceed a specific amount of > voltage. It's also got a unit. For exam