You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
postgres=# \d+ customers
Table "public.customers"
Column │ Type │ Collation │ Nullable │ Default │ Storage │ Compression │ Stats target │ Description
────────┼────────────────────────┼───────────┼──────────┼─────────┼──────────┼─────────────┼──────────────┼─────────────
id │ integer │ │ not null │ │ plain │ │ │
name │ character varying(255) │ │ not null │ │ extended │ │ │
bio │ text │ │ │ │ extended │ │ │
Indexes:
"_pgroll_new_customers_pkey" PRIMARY KEY, btree (id)
"_pgroll_new_customers_name_key" UNIQUE CONSTRAINT, btree (name)
Access method: heap
I guess it's not because we name them like this, but instead because they automatically get their names from the table name. We should either consider renaming them after all is done; or maybe just go with the original name, as there's no point for using a temporary name when creating a table from scratch, so that indexes will get their names without the prefix.
The text was updated successfully, but these errors were encountered:
For CREATE TABLE operation,
Example below:
I guess it's not because we name them like this, but instead because they automatically get their names from the table name. We should either consider renaming them after all is done; or maybe just go with the original name, as there's no point for using a temporary name when creating a table from scratch, so that indexes will get their names without the prefix.
The text was updated successfully, but these errors were encountered: