I think you are right about the encoding. The 8 bytes binary data in the timestamp column looks like this: 0x00000000291A63BF After Sequel has read the data, it becomes \u0000\u0000\u0000\u0000)\u001Ac� Is this the correct encoding? It looks like the translation back to 8 bytes doesn't work for hex values higher than a certain value.
How can I configure the encoding used? Is it possible to have the binary data translated directly to string, like: 0x00000000291A63BF to become "0x00000000291A63BF" -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
