On Tue, Feb 14, 2012 at 7:48 PM, Marc L. Allen <mlal...@outsitenetworks.com>wrote:
> Does the data type start at being the same as the column affinity in the > underlying table and then adjust if the actual data isn't of that type? > i'll have to let someone else answer that, but... > And, if I don't know the underlying table structure, I am guessing that I > should always treat INTEGER as a potential int64? > Assuming your platform supports 64-bit integers, that's probably a safe bet. If you're writing for a target which doesn't support them explicitly (e.g. JavaScript engines traditionally don't) then using double is an option. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users