On 22 Mar 2013, at 3:04pm, Tim Streater wrote:
> Having checked the db carefully, both using hex(col) (via the sqlite3 CLI
> program), and using the unix hexdump utility on the db, I'm now reasonably
> certain that the C2 bytes are simply not in the db. That they show
On 21 Mar 2013 at 23:30, Richard Hipp wrote:
> On Thu, Mar 21, 2013 at 6:52 PM, Tim Streater wrote:
>
>> I have a column defined as TEXT and I insert utf-8 text into it. In
>> particular, there are byte sequences that might look as follows:
>> ... 74 6F
On Thu, Mar 21, 2013 at 6:52 PM, Tim Streater wrote:
> I have a column defined as TEXT and I insert utf-8 text into it. In
> particular, there are byte sequences that might look as follows:
> ... 74 6F 20 C2 A3 32 35 30 ... (in hex)
> which represents:
> ... to £250 ...
>
Simon,
Thanks for the suggestions. I should have mentioned that I'm running under OS X
so I have the sqlite3 application and can easily do the tests you suggest. But
that'll have to be tomorrow - time for shuteye now :-)
Cheers -- tim
___
On 21 Mar 2013, at 10:52pm, Tim Streater wrote:
> I have a column defined as TEXT and I insert utf-8 text into it. In
> particular, there are byte sequences that might look as follows:
> ... 74 6F 20 C2 A3 32 35 30 ... (in hex)
> which represents:
> ... to £250 ...
> I
I have a column defined as TEXT and I insert utf-8 text into it. In particular,
there are byte sequences that might look as follows:
... 74 6F 20 C2 A3 32 35 30 ... (in hex)
which represents:
... to £250 ...
I used Navicat for SQLite Lite to peer at the data as hex and text in the
column, and it
6 matches
Mail list logo