On Thu, 2009-07-30 at 09:18 -0430, An wrote:
> my question stayed unanswered, so that is why i'm repeating it on the
> mailinglist:
> 
> if sqlite2.8 will be supported of bugs the following years, as the web page
> says, what is another reason for working with version 3.x instead of 2.8 ?
> 
> i'm working with xampp-lite server that comes bundled with 2.8... I guess if
> there's no mayor reason i could stay working on 2.8 ?
> 
> is this recommended ?

> thanx

> An M

If I recall correctly, sqlite 2.8 only stored values as text, so if you
are storing lots of numbers, you will be converting back and forth
between text and numeric a lot. Ditto for blobs.

IIRC, bound parameters was introduced in sqlite 3.x, so you run a
greater risk of sql injection attacks using 2.8.

3.x can better handle schema changes invalidating prepared (though I
think they were called "compiled" in 2.8) statements.

3.x I believe handles multiple threads better than 2.8.

I have written program using 2.8 and since they work, I see no reason to
go back and change them.

Hope that helps.
David



_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to