Bronislav Klučka <[EMAIL PROTECTED]> writes:
> PLIIIIIIZ HELP ME
>
>> > > I've read the documentation, where is written: "When the database first
>> > > opened, SQLite reads the database schema into memory and uses that
>> > > schema to parse new SQL statements. If another process changes the
>> > > schema, the command currently being processed will abort because the
>> > > virtual machine code generated assumed the old schema. This is the
>> > > return code for such cases. Retrying the command usually will clear the
>> > > problem."
The easest solution to this problem is to re-open the database when you get
the schema changed error.
If your application must regularly drop and recreate tables, then maybe it's
appropriate to use
DELETE FROM TABLE WHERE 1;
instead of just
DROP TABLE; CREATE TABLE ...;
or
DELETE FROM TABLE;
which will just delete the records without removing the table; i.e. the schema
is not changed this way.
Derrell
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
