Re: New SQLite binary option

2014-11-12 Thread Peter Haworth
Thanks Kay. I reported this as a bug but turns out to be a misunderstanding on the use of revDatabaseColumnNamed. Courtesy of Mark Waddingham, it turns out that if you are getting binary data from the cursor, you need to use the form of revDatabaseColumnNamed that includes the destination

New SQLite binary option

2014-11-11 Thread Peter Haworth
Has anyone used the new binary parameter to revOpenDatabase when opening an sqlite database? It's supposed to store binary data into BLOB columns unchanged - apparently Livecode used to store BLOB's in a proprietary format. Here's what I'm doing: revOpendatabase(sqlite,path to dbfile,binary)

Re: New SQLite binary option

2014-11-11 Thread Peter Haworth
By way of an update on this, the length of the data I supply to the UPDATE statement is around 2.5 million characters. When I read it back in again, it's 244 characters. Obviously there's some severe truncation going on! Question is - is it LC or SQLite? Everything I read on the web says that

Re: New SQLite binary option

2014-11-11 Thread Kay C Lan
On Wed, Nov 12, 2014 at 9:41 AM, Peter Haworth p...@lcsql.com wrote: revExecuteSQL gDBID,Update statement,*btData Have you tried tData without the *b ? I thought the *b was the 'old' way of gettting binary data in SQLite. ___ use-livecode mailing