Thanks for your work.One question: Experimenting with the current beta of Postgres 10 shows that `OWNED BY NONE` is allowed as an option to GENERATEDAS IDENTITY. PermissionsA general problem with the old way is that the system doesn’t actually remember that the user typed serial. So now you can move code around between, for example, PostgreSQL, DB2, and Oracle without any change (in this area). Some have lately been adopting the standard SQL syntax, however. Creating auto-incrementing columns has been a notorious area of incompatibility between different SQL implementations. 😉So why bother? CompatibilityThe new syntax conforms to the SQL standard. do pretty much the same thing, except that the new way is more verbose. and CREATE TABLE testnew (id int GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,payload text) INSERT INTO testnew (payload) VALUES ('a'), ('b'), ('c') RETURNING.
A blog post about it and showed that it works pretty much like serial columns: CREATE TABLE testold (id serial PRIMARY KEY,payload text) INSERT INTO testold (payload) VALUES ('a'), ('b'), ('c') RETURNING. For PostgreSQL 10, I have worked on a feature called “identity columns”.
0 kommentar(er)
