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
Description
By analogy with the string type being converted to varchar, I wanted to limit the length of the number. After the command metasql c, a type integer(<precision>) was generated in the database.sql file, using which will result in an error when attempting to migrate.
Solution
I suggest adding a check that the property length is not used in relation to the type number.
Alternatives
You can also use numeric(<precision>) when generating sql.
Additional context
Driver: Postgres.
The text was updated successfully, but these errors were encountered:
Description
By analogy with the
string
type being converted tovarchar
, I wanted to limit the length of thenumber
. After the commandmetasql c
, a typeinteger(<precision>)
was generated in thedatabase.sql
file, using which will result in an error when attempting to migrate.Solution
I suggest adding a check that the property
length
is not used in relation to the typenumber
.Alternatives
You can also use
numeric(<precision>)
when generating sql.Additional context
Driver: Postgres.
The text was updated successfully, but these errors were encountered: