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
Issue with propel:build fails with phing 2.4.13 #500
Comments
Temporary work around is to specify the phing version 2.4.12 in you're own composer.json.
|
fix #500 update composer.json force phing 2.4.12
Switching to phing 2.4.12 broke generated SQL in my PostgeSQL-based app. All fields are quoted with ". It ends up with errors like this: Undefined column: 7 ERROR: column "ID" does not exist. But my real problem is that when I switch to phing 2.4.13 using my local composer.json file - model is not rebuild… (0 SQL file has been generated) :[ |
@zergu I think your problem didn't come from the phing version change but from another propel change. And I think your issue with phing 2.4.13 is the same as the one reported by this ticket. |
@jaugustin Thanks for the tip. I've checked last commits and there were some about identifier quoting. Disabling it with build property "propel.disableIdentifierQuoting: true" helped. |
There is an issue with the propel:build command since phing released 2.4.13. This has already been reported on the symfony2 mailing list (https://groups.google.com/forum/?fromgroups=#!topic/symfony2/ZZ-Cic57eLI). Here is a copy of the post:
Maybe in the mean time propel should only support 2.4.12 ?
The text was updated successfully, but these errors were encountered: