Richard has it right this time. Today DeviceSQL uses no SQLite code. One of the things we might consider is bolting the SQLite parser/front end to our table engine, in theory to get the both worlds. Just an idea at the moment.
Steve D. Richard Hipp wrote: > > Joe Wilson <[EMAIL PROTECTED]> wrote: >> Be careful about speculative comments. >> >> For all anyone knows, said product could use SQLite internally with >> a couple of proprietary optimizations here and there that may make it >> faster in specific cases. >> >> The sqlite public domain license would allow that sort of thing. >> > > Because of the radically different architectures of SQLite > and DeviceSQL, it seems unlikely that they share a common > core. Though, I suppose anything is possible... > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- > > > -- View this message in context: http://www.nabble.com/DeviceSQL-tp14297970p14327325.html Sent from the SQLite mailing list archive at Nabble.com. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
