-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Usage of unsigned integer in table creation: ACL schema is not recognized by doctrine:schema:validate #44
Comments
I also have this issue. It's is playing havoc with our migration scripts. Is there any way we can help? |
@smilearric do you have any further info about this issue? @javiereguiluz could you let us know if this issue is logged in the right place so that we can help as much as possible? |
@yakobe if you are asking if this is the right repo to report this error ... then you are right. The "Symfony ACL" was taken out of the main symfony/symfony repo, so issues must be reported here. Thanks! |
@yakobe How could I help? What would you like to know? I'm currently on a different project for a few weeks. Since I lose access to the sources in the meanwhile I won't be able to tell you quickly the versions I was running before the issue appeared, if that's what you're after. Otherwise let me know. |
@javiereguiluz thanks for getting back. It seems that making the same changes as daFish/symfony@57694aa does not help. The tables still show changes, just without the "unsigned". It would also make sense since this library was not updated and has not changed in a long time. After some investigation and comparing packages that both I and @smilearric updated, the break seems to occur after updating |
I'm also running into this. |
I install the dev-master version of this bundle. now it's works. |
Hello,
I am getting the exact same problem as the one described here:
symfony/symfony#5108
It has been working fine until I ran
composer update
today. But now:Playing those two command another time each will result in the same output.
I found that the current security-acl bundle actually implements the same specific unsigned integer in its https://github.com/symfony/security-acl/blob/master/Dbal/Schema.php which were causing symfony/symfony#5108 and were removed in daFish/symfony@57694aa and which led to a merge by FabPot back... in 2012.
Dropping / recreating the DB as well as a fresh
composer install
did not fix the problem.More details:
Running within Laragon for Windows 7 with:
DB encoding is
utf8_unicode_ci
. Tried encodinglatin1_swedish_ci
with the same issue.My composer.json might help:
I cannot tell if this has any effect on ACL since I have not yet implemented it.
Anything to do?
Regards
The text was updated successfully, but these errors were encountered: