Quoth Marco <[email protected]>, on 2010-09-28 09:43:17 -0700: > Hello there sqlite-users, > I have a quick question regarding selection and deletion of large unsigned > integers.
No, that---what? SQLite doesn't _have_ "unsigned" integers. Read http://sqlite.org/datatype3.html again and come back once you understand that > I create my table as following: > [1] CREATE TABLE t1 (instnum BIG UNSIGNED INTEGER PRIMARY KEY, ...) > > I then insert some row: > [2] INSERT INTO t1 (instnum, ...) VALUES (CAST (?1 AS BIG UNSIGNED > INTEGER), ...) doesn't do what you think it does (but is accepted syntactically, most likely for a certain amount of compatibility with other database engines). > How can I solve this issue? This isn't something to "solve". If you're working with SQLite, you work with SQLite's types. (Or patch it, if you're really so inclined, but then you may not have interchange capability.) Or if you're binding the query parameters from a language that has unsigned 64-bit integers as a separate data type and doesn't allow implicitly turning them two's-complement, then you might consider it a bug in the binding that bit 63 set becomes a sign bit rather than raising an error, I suppose. I didn't see you mention that anywhere, though. > Thank you, > Marco ---> Drake Wilson _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
