Re: [sqlite] why remove sqlite_encode() ?

Thanks for both responses. I have converted to the new API. - Kervin Quoting "D. Richard Hipp" <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: > > > > Question, why as the encode and decode funtions been removed? > > Did they perform badly, are there bugs? Caveats? > > > > SQLite version 2.8 a

Re: [sqlite] why remove sqlite_encode() ?

[EMAIL PROTECTED] wrote: Question, why as the encode and decode funtions been removed? Did they perform badly, are there bugs? Caveats? SQLite version 2.8 and earlier could not (easily) store binary data - data with embedded \000 characters. Thus the encode/decode routines were provide to transfor

Re: [sqlite] why remove sqlite_encode() ?

If you use BLOBs I do not think you need sqlite_encode_binary and sqlite_decode_binary On Tue, 2004-10-05 at 02:30, [EMAIL PROTECTED] wrote: > Hello, > > I am new to sqlite. So far I've been very impressed by it. We > are using it as the backend of an open-source MAPI message store. > Still str

[sqlite] why remove sqlite_encode() ?

Hello, I am new to sqlite. So far I've been very impressed by it. We are using it as the backend of an open-source MAPI message store. Still struggling with locking issues, but looking alright. Question, why as the encode and decode funtions been removed? Did they perform badly, are there bug