Patricia G. wrote: > Hi Andy, > > > Having a generic table with key value pairs like your current info > table > just leads to some really horrible SQL as you are currently finding. > > > > I agree with you . > > Unless you truly don't know what key-value pairs you are going to store > it's always best to design your table to store the specific values > > > In the beginning I wanted to design something similar to what you > suggest, but the problem is that it is hard to determine the values that > will be stored into the database. There will be times when I will not > get 'release' or 'arch' information. > > Thanks, > Patricia >
Thats what NULL is for. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
