On Wed, Sep 13, 2017 at 10:49 PM, Noah Misch <n...@leadboat.com> wrote: >> > Both Oracle and MySQL allow finite values after MAXVALUE (usually >> > listed as "0" in code examples, e.g. see [1]). Oracle explicitly >> > documents the fact that values after MAXVALUE are irrelevant in [1]. >> > I'm not sure if MySQL explicitly documents that, but it does behave >> > the same. >> > >> > Also, both Oracle and MySQL store what the user entered (they do not >> > canonicalise), as can be seen by looking at ALL_TAB_PARTITIONS in >> > Oracle, or "show create table" in MySQL. >> >> OK, thanks. I still don't really like allowing this, but I can see >> that compatibility with other systems has some value here, and if >> nobody else is rejecting these cases, maybe we shouldn't either. So >> I'll hold my nose and change my vote to canonicalizing rather than >> rejecting outright. > > I vote for rejecting it. DDL compatibility is less valuable than other > compatibility. The hypothetical affected application can change its DDL to > placate PostgreSQL and use that modified DDL for all other databases, too.
OK. Any other votes? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
