-
Notifications
You must be signed in to change notification settings - Fork 161
SQL schema update cause some troubles. #170
Comments
Duplicate of #168 |
I understand that you consider this as a duplicate. #168 is talking about wrong default values in It's just to keep you aware that there is more than one change to do. |
@cyrilf are you eventually able to provide a test case for the issue? |
@Ocramius unfortunately not.. I've started working with ZF2 only a week ago. So I'm not aware about best practices and how to easily do that. But if you need me to be more precise about the issue I encounter I'm glad if I can help. Edit:I've created a Gist to show you my workaround (just using a join between the 2 tables). |
@cyrilf ah, I see the problem. It looks like a valid fix, but I will include it only with tests. |
Hello, when do you plan to release a working version? |
Whenever someone provides a patch+test plus I have time to merge it
|
Tell me, please, what version is still working? |
Well done, thank you. |
Will fix asap
|
@dphn fyi, you can directly comment on the diff |
Er ... comments? Now three tables. A one role have a single parent. If done four tables, one role can have multiple parents :) |
@dphn can you please comment on the correct issue, inline, in the location that bothers you? I am not understanding the problem you are trying to explain. |
The correct thread is #171 |
Handled @8214a324c3307f6675e8c38228e4b304ceb29fc8 |
@Danielss89 has done a pull request (164) in order to update the schema.sql
Now, the documentation isn't up to date and some files haven't been updated accordingly..
My main issue is with the
Provider/Identity/ZfcUserZendDb.php
in the methodgetIdentityRoles
This method should return a string corresponding of the roleId but now, it returns an int and ZF doesn't know this role (as it receive an id like: 7 instead of a name like 'admin').
My workaround for now is to use this id (i.e. 7) and query the
user_role
table in order to get the corresponding string (i.e. admin)The text was updated successfully, but these errors were encountered: