I see no unsigned integer support anywhere ... https://www.sqlite.org/datatype3.html
And there are no API functions dealing with unsigned integers, only standard 2-s complement signed integers. https://www.sqlite.org/c3ref/funclist.html Declaring something an "unsigned integer" is the same as declaring it an "unsinged integer". The substring "int" declares the affinity and the rest is ignored as line noise. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of Warren Young >Sent: Saturday, 30 June, 2018 18:09 >To: SQLite mailing list >Subject: Re: [sqlite] column types and constraints > >On Jun 29, 2018, at 10:17 PM, Keith Medcalf <kmedc...@dessus.com> >wrote: >> >> So what you really want is (a) to be able to error-out on SQL >operations that do not use proper affinity words (ie, only accept >INTEGER, DOUBLE, TEXT and BLOB), and; (b) to crash or return an error >instead of converting the data that you put or at least, that you >ask. > >That would work, too. > >There’s a schools of thought that says that “unsigned” should just go >away, that it causes more trouble than it’s worth. > >I believe the only reason SQLite supports it is to ease conversion of >schemas from other DBMSes. >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
