Update #7303
Failed: PDOException: SQLSTATE[42804]: Datatype mismatch: 7 ERROR: argument of AND must be type boolean, not type integer LINE 2: WHERE (path ILIKE 'admin/%' ESCAPE '\\') AND (type & '128')... ^: DELETE FROM {menu_router} WHERE (path ILIKE :db_condition_placeholder_0 ESCAPE '\\') AND (type & :db_condition_placeholder_1) ; Array ( [:db_condition_placeholder_0] => admin/% [:db_condition_placeholder_1] => 128 ) in admin_menu_update_7303() (line 98 of /sites/all/modules/admin_menu/admin_menu.install).
Problem with conditional fragment (type & '128'). Its result's type is integer and PostgreSQL forbids such clauses `(boolean AND something_that_cannot_be_implicitly_casted_to_boolean)'. And integer can't be implicitly casted into boolean. The _right_ clause is something like that: ( type & 128) = 128
Sorry fo my terrible English...
| Comment | File | Size | Author |
|---|---|---|---|
| patch-7303-update-psql-fail.patch | 522 bytes | suvisor |
Comments
Comment #1
izzmo commentedThe patch submitted suvisor works for me.
Comment #3
fastcat.org commentedPatch works for me too. If you look at the test failure, it doesn't apear to have anything to do with the patch, or even the admin menu test cases it's trying to run:
FATAL CtoolsPluginsGetInfoTestCase: test runner returned a non-zero error code (255).Comment #6
truls1502I am sorry for no reply until now.
There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.
We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.
However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.
So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?
Thank you for understanding! :)
Comment #7
truls1502This issue has been automatically marked as closed because it has not had recent activity after the last post.
However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.
Again, thank you for your contributions.