You should also consider how your change might effect
backwards compatibility. The last time that table_info()
was modified, the Ruby-On-Rails community got really
upset. I'm rather of a mind to leave table_info() alone.
Forgive my ignorance, I'm just a beginner in databases,
but what about TABLE_INFO2 ( ) ?
(with the explicit restriction that it can be extended in the future
when needed,
so Ruby users leave it alone ;-)
I really can't imagine that extension of a function can cause serious
compatibility issues)
The alternative is now that I've to
- build a table from table_info()
- query sqlite_master, to get the SQL string with which the table was
generated
- parse the SQL string from sqlite_master
- and add it to my edit grid form table_info
or are there simpler ways ?
--
cheers,
Stef Mientki
http://pic.flappie.nl
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
