Re: [sqlite] XML translation inquiry

ch Andrew Piskorski wrote: On Thu, Apr 15, 2004 at 02:37:13PM -0400, rich coco wrote: the goal would be to abstract out of the application the entire DB schema and allow the application to work exclusively with XML - and the generated methods - wrt not only data representation and transport but

Re: [sqlite] XML translation inquiry

please tell me more...as in why it's a bad idea. performance? are the in-memory translations really that cpu intensive? what if the data sets are never very large? thanks, - rich Andrew Piskorski wrote: On Thu, Apr 15, 2004 at 01:47:01PM -0400, rich coco wrote: the goal would be to abs

[sqlite] XML translation inquiry

the specifics regarding data persistence, etc. google-ing hasn't helped me here, but that may be because i'm not google-ing smartly. i am open to suggestions as to where else I might post such a query. tia, - rich -- rich coco [EMAIL

[sqlite] ENUM semantics

upported, I would have expected the error to be 'SQL error: near "enum"...' I've tried using double-quotes instead of single-quotes... same error. Anyway, how *does* one define the ENUM semantic in SQLite?

[sqlite] mySQL to SQLite conversion question

ny out there and I'd like to purchase just one, so I need to get it right the first time. I found on-line manuals by DB engine providers - eg, http://www.mysql.com/doc/en/SQL_Syntax.html - but I do not know when I may be looking at specialized extentions (eg, mySQL's REGEXP and auto_increme

[sqlite] moving from mySQL to SQLite - A guidance request

e DB operations? What about existing SQL statements (explicit arguments to mysql function calls) that use SQL keywords/contructs (eg, REGEXP) not supported by SQLite? Is there a best-practices way of doing this kind of transition from one DB to another? advice welcome. -- rich coco [EMAIL PROTECTE