Closed daniele-olivieri-rs closed 6 months ago
Hello @daniele-olivieri-rs ,
Thank you for your bug report. This issue has been addressed and fixed in v8.0.4.1. Please update the package and verify if it works.
Please be advised, that if you are using migrations, then after upgrade next added migration will change column type from NUMBER(38,18)
to NUMBER(18,2)
in your case.
Thanks @Sielnix!
When generating a DbMigration model-first, nullable decimals ignore the
precision
andscale
in thetype
string.For example:
Produces this in the DbMigration:
Notice,
type
is"NUMBER(38,18)"
instead of"NUMBER(18,2)"