Question remains if it isn't better to go to a new major version on such
changes.
Forward compatibility is assumed by users imo.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <sqlite-users@sqlite.org>
Sent: Tuesday, June 27, 2006 1:08 PM
Subject: Re: [sqlite] v3.2.1
TED]>
To: <sqlite-users@sqlite.org>
Sent: Monday, June 26, 2006 8:20 PM
Subject: Re: [sqlite] v3.2.1 and current differences!
"Edwin Knoppert" <[EMAIL PROTECTED]> wrote:
Just wanted to warn you i can not read a newly created table created with
the current release and opening it
Peter Bierman <[EMAIL PROTECTED]> wrote:
> At 2:20 PM -0400 6/26/06, [EMAIL PROTECTED] wrote:
> >SQLite 3.3.0 can read and write all prior versions of SQLite
> >databases. But SQLite 3.2.8 cannot read or write a database
> >created by SQLite 3.3.0, unless you use
> >
> > PRAGMA
"C.Peachment" <[EMAIL PROTECTED]> wrote:
> You can create the database with the older Sqlite version, but any use
> with the new version must be preceded by the pragma, otherwise the
> new version changes the data format, making it unreadable by the
> old version thereafter.
>
The file format is
At 2:20 PM -0400 6/26/06, [EMAIL PROTECTED] wrote:
SQLite 3.3.0 can read and write all prior versions of SQLite
databases. But SQLite 3.2.8 cannot read or write a database
created by SQLite 3.3.0, unless you use
PRAGMA legacy_file_format=TRUE;
prior to creating the database, or unless you
"Edwin Knoppert" <[EMAIL PROTECTED]> wrote:
> A bit odd the system does not handle backwards compatibility in minor
> releases.
>
It *does* handle backwards compatibility. It is forwards
compatibility that causes problems.
Newer versions of SQLite can read databases generated
by all older
e pragma helps anyway..
>- Original Message -
>From: "C.Peachment" <[EMAIL PROTECTED]>
>To: <sqlite-users@sqlite.org>
>Sent: Monday, June 26, 2006 8:16 PM
>Subject: Re: [sqlite] v3.2.1 and current differences!
>> On Mon, 26 Jun 2006 20:03:35 +0200, Ed
o: <sqlite-users@sqlite.org>
Sent: Monday, June 26, 2006 8:16 PM
Subject: Re: [sqlite] v3.2.1 and current differences!
On Mon, 26 Jun 2006 20:03:35 +0200, Edwin Knoppert wrote:
Just wanted to warn you i can not read a newly created table created with
the current release and opening it in
"Edwin Knoppert" <[EMAIL PROTECTED]> wrote:
> Just wanted to warn you i can not read a newly created table created with
> the current release and opening it in v3.2.1 (afaik)
>
> Sorry, i removed the older dll, i overwrote it with the latest and read the
> table instantly.
> Before i had 0
On Mon, 26 Jun 2006 20:03:35 +0200, Edwin Knoppert wrote:
>Just wanted to warn you i can not read a newly created table created with
>the current release and opening it in v3.2.1 (afaik)
>Sorry, i removed the older dll, i overwrote it with the latest and read the
>table instantly.
>Before i
Just wanted to warn you i can not read a newly created table created with
the current release and opening it in v3.2.1 (afaik)
Sorry, i removed the older dll, i overwrote it with the latest and read the
table instantly.
Before i had 0 tables shown.
A simple query was used:
CREATE TABLE
11 matches
Mail list logo
