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
A user should able to select serial datatype along with all the other data types.
With the release of the custom primary key, it becomes necessary to make "Serial Type" available as a data type. Since Serial type is an auto-generated auto-incremented field, it will have the following properties
It cannot have a default value. Therefore upon selecting "Serial" field type, the default value input field for the column will become disabled.
It has NOT NULL and UNIQUE constraints by design in Postgres. Therefore, upon selecting "Serial" field type, these constraints will also reflect on UI.
Copywriting for serial datatype: Serially generated integers
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
Serially generated integers are only part of the id column and can't be picked up by the user for any other columns
Describe the solution you'd like
PRD: link
ADR: link
Design: link
A user should able to select serial datatype along with all the other data types.
With the release of the custom primary key, it becomes necessary to make "Serial Type" available as a data type. Since Serial type is an auto-generated auto-incremented field, it will have the following properties
Copywriting for serial datatype:
Serially generated integers
The text was updated successfully, but these errors were encountered: