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
For auto-generated values, we could send additional information based on how we intend to support formulas, procedures and functions in the future. For now, we can just send the same value and on the frontend the input can be disabled.
The text was updated successfully, but these errors were encountered:
As for the cruddy-looking output for dynamic defaults, I'm thinking we just use that for now so the user can at least see what's happening if they know how it works. We'll need to do other things when we have the ability to work with dynamic defaults better.
Description
When the default value is auto-generated, the returned value is a string representing the procedure call.
Eg., for all PKs for the default id column, the value for
default
is"nextval('\"public\".data_types_id_seq'::regclass)"
.We need additional information to help the client differentiate this from a normal string value.
Expected behavior
It would be better if default returned an object, something similar to:
For auto-generated values, we could send additional information based on how we intend to support formulas, procedures and functions in the future. For now, we can just send the same value and on the frontend the input can be disabled.
The text was updated successfully, but these errors were encountered: