On 29 Jun 2018, at 9:23pm, Thomas Kurz <[email protected]> wrote:
> a) Why would I put strings in an integer column? If I need to do so, I have a > concept error in my database schema. > > b) I think that noone wants type affinity to be actually removed. I'd just > like an option to make SQLite behave like any other DBMS and > - respect the data type declared for a column > - reject column definitions with invalid types (e.g. "STRING") Here's the question: do you want consistency or do you want safety ? If you try to put TEXT into a REAL column you should get an error message, right ? If you try to put REAL into an INTEGER column, you should get an error message, right ? Or not ? Do you want automatic truncation rather than an error message ? Do you know what PostgreSQL, Oracle, Informix, DB2, MS-SQL, OCELOT, MySQL, Firebird, SQL Anywhere, and Borland Interbase do ? Do you want compatibility with all of them ? Those are rhetorical questions. I don't really want you to answer them. But I'm trying to point out that the SQL standard doesn't say what should happen and many other SQL engines have made their own choices. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
