-
Notifications
You must be signed in to change notification settings - Fork 397
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
Regression in Builder Breaks Generated Entities #1324
Comments
I don't think #1090 is responsible for this. Can you give me your schema.xml that generates that wrong php code? |
Thanks for the quick response. The issue doesn't occur with Propel 2.0.0 alpha5 though |
You were right, #1090 was buggy. I fixed it in master. |
Thanks a lot for taking care of it so quickly. Do you have an ETA on a new release that contains this fix? |
Thanks for the awesome support! It is highly appreciated 👍 |
The alpha 6 release introduced a regression in the generation of entity files. It's very likely due to this change: #1090
We recently updated Propel to version alpha 6 at Spryker an are seeing issues with platforms supporting native id-method auto-increment (e.g. MySql).
It seems that the changes applied to
DefaultPlatform::getIdentifierPhp()
(https://github.com/propelorm/Propel2/blob/2.0.0-alpha6/src/Propel/Generator/Platform/DefaultPlatform.php#L1347) are not in sync with how this method gets called inObjectBuilder::addDoInsertBodyRaw()
(https://github.com/propelorm/Propel2/blob/2.0.0-alpha6/src/Propel/Generator/Builder/Om/ObjectBuilder.php#L5887).The results in the generated entity files look something like this:
$pk = $con'foo-pk-seq'->lastInsertId();
which results in a critical parse error.
Thanks for looking into it.
The text was updated successfully, but these errors were encountered: