But please don't do this! The resulting database files will NOT be sqlite database files.
You won't be able to look at them on other systems (or even using the 'real' library on the same system). Thanks Steve Shane Harrelson wrote: > If you're really serious about storing your data in a "native" form to > reduce read/write overhead for handling endian-ness (and I think this is > going to be more trouble than it's worth) then you can look at replacing the > following functions in vdbeaux.c: > > ** sqlite3VdbeSerialType() > ** sqlite3VdbeSerialTypeLen() > ** sqlite3VdbeSerialLen() > ** sqlite3VdbeSerialPut() > ** sqlite3VdbeSerialGet() > > You can probably get by with just replacing put/get which for integer and > real types break up the value into a series of bytes and read/write those > to/from a passed buffer in big-endian order. > > HTH. > -Shane > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
