I've been using sqlite for several months now and have never had a SQLITE_SCHEMA error. What are you doing that's causing it?
On 4/21/05, Vladimir Vukicevic <[EMAIL PROTECTED]> wrote: > Right now it's quite difficult to implement any kind of higher-level > wrapper over sqlite3_prepare()/sqlite3_step()/etc., because of the > semantics of the SQLITE_SCHEMA error. If you bind values to > parameters of a sqlite3_stmt, you have to redo that binding after you > recreate the sqlite3_stmt due to SQLITE_SCHEMA. This is cumbersome, > because it means that you have to expose essentially SQLite internals > into user code, and the user code has to loop around every statement > until it succeeds or errors out with something other than > SQLITE_SCHEMA. Is there any reason that step() can't recreate the > bits of the VDBE that need to be updated itself in case of a > SQLITE_SCHEMA error, while preserving current parameter bindings? > > Thanks, > - Vlad > -- --- You a Gamer? If you're near Kansas City: Conquest 36 https://events.reddawn.net The Castles of Dereth Calendar: a tour of the art and architecture of Asheron's Call http://www.lulu.com/content/77264
