Re: [sqlite] 3.1 vs. 3.0 file compatibility.
--- [EMAIL PROTECTED] wrote:
> On Jan 21, 2005, at 2:49 PM, Dan Kennedy wrote:
> > If the 3.1 file is created with the auto-vacuum option enabled
> > ("PRAGMA auto_vacuum = 1;"), then the database will appear read-only
> > to 3.0 clients. That's the only incompatibility.
>
> OK -- can auto-vacuum be turned on within a database that was created
> with 3.0?
No. Auto-vacuum cannot be turned on after a database has been created.
__
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com
Re: [sqlite] 3.1 vs. 3.0 file compatibility.
On Jan 21, 2005, at 2:49 PM, Dan Kennedy wrote:
If the 3.1 file is created with the auto-vacuum option enabled
("PRAGMA auto_vacuum = 1;"), then the database will appear read-only
to 3.0 clients. That's the only incompatibility.
OK -- can auto-vacuum be turned on within a database that was created
with 3.0?
b.bum
smime.p7s
Description: S/MIME cryptographic signature
Re: [sqlite] 3.1 vs. 3.0 file compatibility.
On Fri, 2005-01-21 at 14:38 -0800, [EMAIL PROTECTED] wrote: > Under what circumstances is a file written by 3.1 incompatible with a > file written by 3.0? > When the database uses features that 3.0 does not support. For example, if a VIEW definition uses the new EXISTS operator, an older 3.0 library would not be able to parse the VIEW when it initializes. I anticipated autovacuum. So 3.0 knows about autovacuum and can read an autovacuumed file. It just can't write it. And it knows not to try.
Re: [sqlite] 3.1 vs. 3.0 file compatibility.
If the 3.1 file is created with the auto-vacuum option enabled
("PRAGMA auto_vacuum = 1;"), then the database will appear read-only
to 3.0 clients. That's the only incompatibility.
--- [EMAIL PROTECTED] wrote:
> Under what circumstances is a file written by 3.1 incompatible with a
> file written by 3.0?
>
> thanks,
> b.bum
> ATTACHMENT part 2 application/pkcs7-signature name=smime.p7s
__
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
[sqlite] 3.1 vs. 3.0 file compatibility.
Under what circumstances is a file written by 3.1 incompatible with a file written by 3.0? thanks, b.bum smime.p7s Description: S/MIME cryptographic signature
