On 22 Oct 2013, at 4:47pm, Michael Foss <[email protected]> wrote:
> Other solutions I have considered, but have decided are undesirable: 4) Copy the code of SQLite but in your copy change the part of the code which formats a REAL for writing to disk and the part of the code which reads it back again. Preferably include a test in sqlite3_initialize() or sqlite3_os_init() to see if you're running on your weird processor, then check that flag later when implementing the routine that prepares bytes for disk. It might be possible to do this just by writing your own VFS. I'm not familiar with that level of how SQLite works but others here are. Perhaps all you need to do is have that processor use your own non-standard VFS and not modify the basic SQLite code. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
