On Tue, Apr 22, 2014 at 8:25 PM, Dominique Devienne <ddevie...@gmail.com>wrote:
> Yet I don't see the point of a BIGINT either. A blob can effectively > act as a arbitrary sized integer already, albeit one stored in base > 256 and on which you cannot do arithmetic, but that's OK and enough to > use it as a PK / FK. > A blob can store raw binary data, i.e. raw integers from memory. Just be sure to encode/decode them if you want their stored representations to be platform-portable (big vs little endian). You can bind a blob using (&myInt, sizeof(myInt)) if you really want to, it just won't be platform-portable without settling on an encoding. If the goal is only performance, though, it might (without encoding) be (marginally) faster than using string-format data (be sure to use SQLITE_TRANSIENT when binding the memory, too). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
