On Tuesday 15 Nov 2005 1:39 pm, panos wrote: > I don't know if it is strange or not, but it came to me as a natural > choice for my application. > Think of a logging application where some variables need to be logged > and we need a table for > each variable holding a great number of "timestamp - value" entries. > The thing is we don't know beforehand which variables we need to log, > but the app user specifies that dynamicaly. These variables > could be hundreds or even thousands so it doesn't make sense to > create a table at the beginning > for each and every one of them. I want to be able to create a new > table at runtime as soon as a new > variable is selected for logging.
this is actually an sql issue - but you need two tables: table log: fields: id, variablename table logdetails: fields: id, foreignkey(variablename), timestamp, logentry every new variable is added to 'log' table and log entries for it go in the 'logentry' table. -- regards kg http://www.livejournal.com/users/lawgon tally ho! http://avsap.org.in ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
