> Are you looking for a way to add extra data to existing rows in a table > without having to add new columns? I have been thinking about doing > something like this for an app I maintain at work. Basically I would > create another table and call it tablename_properties where 'tablename' > is the name of the table I'm adding properties for. It would contain > four columns: > - ID -- the primary key > - tablenameID -- foreign key linking each row to a primary key in the > 'tablename' table > - property -- this holds the name of the extension > - value -- this is a text or blob field that holds the extension data
This is a pretty common approach ( we use it to hold translation data for tables ). Spectra used a similar model for its schema. The downside is that it makes all of your sql code more comlex, and you need to post process the data after you've gotten it out. I think its worth looking at why you want to have per row mutability of the schema, and decide whether its really necessary, or if its just a cunning way of doing things. If its practical, you are probably better served with some schema evolution scripts. Jon. --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
