Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Content inserted into the column with a datatype other than ANY must be either a NULL (assuming there is no NOT NULL constraint on the column) or the type specified. SQLite attempts to coerce the data into the appropriate type using the usual affinity rules, [...].

I would like an even stricter mode with no automatic type coercion.



Not trying to be mean, but it's like when someone who doesn't understand the point of the feature implements it.


I don't understand your point; I'm not sure why.


I think they mean that your up-thread (is that OP or GP or?) comment is asking for the wrong thing. Like one of those XY type problems


I always underestimate how easy it is to be misunderstood. Why it's worthwhile to spend time on clear communication!

I'm chiding SQLite, a bit unfairly, that they only implemented the strict feature half right, still leaving some type coercion in.


Thanks, I understand your point now, and I agree. The SQLite3 devs seem to think that because other SQL RDBMSes do this, they should too. At this time I'm of the opinion that more strictness is better.


Which other SQL engines do this? The ones I'm familiar with (MySQL, PostgreSQL, Microsoft SQL, Orcale to name a few) certainly don't behave anywhere close to how SQLite behaves.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: