4 ms·
So what would be wrong with the following announcement: "In three years, varchar no longer takes an argument, char and money do no longer exist, psql's passwor
by lucb1e 8y ago
So what would be wrong with the following announcement:
"In three years, varchar no longer takes an argument, char and money do no longer exist, psql's password flag will be removed, all tables will be lowercased, BETWEEN will require fully qualified values, table inheritance will be disabled unless you specify a config value, and this page will be shortened to only include NOT IN and SQL_ASCII. In one year, a lot of these things will raise warnings. In two years, it will raise suppressible errors."
(I left out a few for brevity, but only a few -- this would actually resolve most of this page.)
Most of this strikes me as common things (varchar and psql --password in particular), and aside from NOT IN there appear to be easy solutions to make people stop using it without big changes. It's not like python3 where you have to change a core thing like text handling, it's removing a flag from your cronjobs (--password), omitting a value (varchar(n)), or telling the database what you really meant (BETWEEN X AND '2019-01-01' -> '2019-01-01T23:59:59.999'). For stuff without obvious fixes, a "do not do this" page is much more reasonable.
- perlgeek 8y agoI'm sure that there are far too many use cases of varchar(255) out there for anybody to deprecate such a feature without causing huge pain to everybody involved. Just look at the python 2 to python 3 transition, which is still ongoing, more than 10 years after the python 3.0 release. Also, warnings usually simply don't work. Developers or admins google the warning, see that it can be switched off, and switch it off. DDL is often generated (for example for migrations), and you might not want to add a special case for postgres if you can avoid it. Suppressing a warning is definitively easier than changing code generation in potentially non-compatible ways. Plus, I haven't looked it up, but given how prevalent VARCHAR(N) is, it might be part of the SQL standard.
- losvedir 8y agoWhat's wrong with it is this is a database and not a JavaScript framework flavor of the week.