Hi, ALL, I am not sure what are we talking about here and is discussed. Just like on the paper the hard drive is storing the characters. It is for us (humans, developers) to interpret those characters as a TEXT, numeric value (be it INTEGER or FLOAT/DOUBLE) or some binary data.
As long as the client retrieves the exact set of characters that was stored (and it is) there is nothing to talk about. Because this is exactly what the database is for - store some data for the future use. The strong typing in the DBMSes are there to simplify the life of the people who creates the library which is used by the actual developers to create client application. Nothing more, nothing less. Just imagine if MS Access had the affinity paradigm instead of strong data types. How hard would be to write the VB for Access for MS devs. So once again - it is exactly as on the paper - characters that should be interpreted by people (developers). Thank you. P.S.: I hope I'm right here and if not someone will surely correct me. On Sat, Jun 30, 2018 at 3:57 PM, Keith Medcalf <[email protected]> wrote: > > In your case, yes. > > If you do not wish SQLite3 to "convert" to the requested storage type on > storage of a value, then do not specify a storage type (or specify a storage > type of BLOB). Then whatever you request-to-store will be stored without > conversion. > > SQLite version 3.25.0 2018-06-21 23:53:54 > Enter ".help" for usage hints. > Connected to a transient in-memory database. > Use ".open FILENAME" to reopen on a persistent database. > sqlite> create table x(x); > sqlite> insert into x values ('3'); > sqlite> insert into x values ('3.0'); > sqlite> insert into x values (3); > sqlite> insert into x values (3.0); > sqlite> insert into x values (x'123456789084759301939875459381798754'); > sqlite> insert into x values (null); > sqlite> select x, typeof(x) from x; > 3|text > 3.0|text > 3|integer > 3.0|real > 4Vx��u� ��uE��y�T|blob > |null > sqlite> > > --- > 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- >>[email protected]] On Behalf Of Thomas Kurz >>Sent: Saturday, 30 June, 2018 14:10 >>To: SQLite mailing list >>Subject: Re: [sqlite] column types and constraints >> >>> when in fact it was the third-party interface wrapper. >> >>The examples I provided were all taken from the current sqlite3.exe >>cli with 3.24.0 library. It is not a third-party issue. >> >>_______________________________________________ >>sqlite-users mailing list >>[email protected] >>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
