ok, the sqlite_Schema thing can (and has) been wrapped. however, the error code issue is there, I believe that we have agreed in the past that it was bad design, but it could not be changed because of compatibility issues. I,for one, am willing to comb my code and re-code for this, so yes, please do it.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 03, 2005 4:05 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Request for comment: Proposed SQLite API changes > > Dan Kennedy <[EMAIL PROTECTED]> wrote: > > > Another proposal: Suppose that when creating an > sqlite3_stmt using > > > sqlite3_prepare, the original SQL text was stored in the > > > sqlite3_stmt. Then when a schema change occurred, the > statement was > > > automatically recompiled and rebound. > > > > The authorization callback > > would have to be reinvoked from within sqlite3_step() too. > > Yikes! I didn't think of that. This is pretty big negative > and will likely scuttle plans to do automatic re-prepare. > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > >
