Strange warning appears after installing drake and cakePHP
ichabooka - January 23, 2008 - 21:52
| Project: | Drake :: Drupal-CakePHP bridge |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I see this warning at the top of the page now after installing cakePHP and Drake to my existing Drupal installation:
user warning: Duplicate entry '' for key 1 query: UPDATE sessions SET sid = '' WHERE sid = 'drake_9htqmusg74fil9dpt26ks67ot4' in /usr/local/apache2/htdocs/includes/database.mysql.inc on line 172.
I seem something similar to this on all pages. What's causing this and how do I fix it?
Thanks,
Sean
#1
I'm experiencing the same error. Help!
#2
help i happen to be in the same shoes
what is the solution
#3
according to my experiments it seems drake doesn't fully support cake session
this errors occurs if you try to use session but right now i dont have a solution but i'm trying to find it
#4
Same problem with me.
#5
Well after my experiments i finally discovered the following:
drake generates the same session id anytime you use it to run your cakephp, and this id is logged into the session table in your drupal database and the sid(column responsible for logging each session id) is a unique column, the only solution is to remove the unique attribute on the sid column and the error is gone.
This works if you are using a postgres database i should work with mysql database.
caution: I have not fully examine the aftermath of this but it works and the error is gone with no crashes!!
#6
Hello Asare, how is your custom solution working??? Have you experienced any problems due to the change in the database??? I am very interested.
#7
Hi, Asare
Can confirm works same on mySQL.
As a newbie, I am attempting to customise Drake for personal use on Drupal 6.2 - can get most working but have had the odd code crash this afternoon which caused the duplicate session entries.
I have just been clearing the session table completely, logging in again and continuing with no apparent side effects. Drupal recreates session entries in table. As a sideline, also have noticed that clearing cache under site config/performance does not completely clear cache entries - have to manually gut these entries (multiple tables) some times to get new code visible on screen.
Still some Drake customisation issues - cake comes up in a separate window - yet to solve that one.