Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DBAL-44] Fix column default value lifecycle #456

Merged
merged 1 commit into from
Dec 22, 2013

Conversation

deeky666
Copy link
Member

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.

@doctrinebot
Copy link

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DBAL-720

We use Jira to track the state of pull requests and the versions they got
included in.

@AdamWill
Copy link

Can this go to 2.4 branch, or is it too large? Owncloud is carrying an earlier version / subset of this fix downstream:

owncloud-archive/3rdparty@12d8399

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants