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

[WIP] Update doctrine/dbal to 2.5.1 #13537

Closed
wants to merge 4 commits into from
Closed

[WIP] Update doctrine/dbal to 2.5.1 #13537

wants to merge 4 commits into from

Conversation

VicDeo
Copy link
Member

@VicDeo VicDeo commented Jan 20, 2015

Closes #13303
Depends on owncloud-archive/3rdparty#152

Scheduled for 8.1

@DeepDiver1975
Copy link
Member

@VicDeo thx - can you please have a look at the failing unit tests? Looks like something changed which breaks on our side - THX

@DeepDiver1975 DeepDiver1975 added this to the 8.1-next milestone Jan 20, 2015
@VicDeo
Copy link
Member Author

VicDeo commented Jan 20, 2015

@DeepDiver1975 yes, there are breaking changes with index handling. https://github.com/owncloud/3rdparty/blob/dbal-251/doctrine/dbal/UPGRADE.md

Will have a look

@scrutinizer-notifier
Copy link

A new inspection was created.

@VicDeo
Copy link
Member Author

VicDeo commented Jan 27, 2015

@DeepDiver1975 This is what we call a breaking change: indexes with the same name are compared by some additional features

doctrine/dbal@c1eae73
doctrine/dbal@32fae86

An autoincrement field is always a primary index and according to a new 'smart' logic no more primary indexes are allowed for tables with autoincrement:
https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Schema/Table.php#L508

So there is a definition conflict between https://github.com/owncloud/core/blob/master/db_structure.xml#L1208 and https://github.com/owncloud/core/blob/master/db_structure.xml#L1245

@DeepDiver1975
Copy link
Member

oh - brilliant!

05466030

@DeepDiver1975
Copy link
Member

I'll have a look once 8.0 has left - THX @VicDeo

@DeepDiver1975
Copy link
Member

@VicDeo did you find any solution already to these problem? This is kind of getting momentum - see #14003 - please put some prio on this - THX

@karlitschek
Copy link
Contributor

How risky would be a 8.0.1 backport? #14003 Sounds not good.

@DeepDiver1975
Copy link
Member

From my pov the risk depends on the amount of adjustments. Maybe a selective patch could be an option for oc8.0.1
But let's get 2.5.1 working first.

@ghost
Copy link

ghost commented Feb 11, 2015

Refer to this link for build results (access rights to CI server needed):
https://ci.owncloud.org//job/pull-request-analyser-ng-simple/9215/
Test FAILed.

@VicDeo
Copy link
Member Author

VicDeo commented Feb 11, 2015

Something went fubar here.
Resubmitted as #14119

@VicDeo VicDeo closed this Feb 11, 2015
@VicDeo VicDeo deleted the dbal-251 branch February 11, 2015 16:50
DeepDiver1975 added a commit that referenced this pull request Feb 23, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dbal 2.5.1 has been released - we should consider updating
5 participants