This is an approach to make the "lifecycle" of a column's default value more consistent and less error prone. It also fixes some platform implementations, especially when a column's default value has to be dropped (which requires an explicit drop clause on some vendors).
This implementation implies a default value of null as no default value set. All other values get evaluated as a default value.
fix column default value lifecycle
thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:
We use Jira to track the state of pull requests and the versions they got
Can this go to 2.4 branch, or is it too large? Owncloud is carrying an earlier version / subset of this fix downstream:
we (Fedora) would be happy if we can get all of OC's downstream patches to DBAL merged into the 2.4 branch, then update our DBAL to 2.4 and have OC use it.