Jan Škrášek
Jan Škrášek
In such case the exception is a must have. This could cause serius security issue.
Of course, but we are talking about silent security issue.
Not sure if this is a good idea. In the end, the majority will still convert it to float, manually or by php auto-coercion.
> For „normal“ float numbers you should just use real / double precision type. This describes exactly the problem. The normal float are just regular floats where actually almost nobody...
The latest recent news is that there will be a setter for explicit conversion type. WIP here: https://github.com/nextras/dbal/commit/ea47124657be658775e65713e99ebaafd16d7ae2
Thanks for reporting this. agreed that it would be ideal to handle this automatically. I will have to study what are all cases when the rollback happens automatically.
Great! I was thinking about similar solution of storing such thing into separate file... :)
I have a different idea. What we want is the security, that prevent's us from merging pull request if it contains migrations which is not the last. Such check may...
> We may consider a requirement that the database must be initially empty. Yeah, but that may be quite difficult. Though, I prefer the higher security over the usability.
Time to start with https://github.com/nextras/db-importer, use https://github.com/lacanoid/pgddl, ...