Closed bluesnowman closed 11 years ago
@CubedEye Got any ideas regarding this issue?
I'll have a look...
It looks like the DB ENGINE and CHARSET could be the issue. Also maybe the session_id/id field.
Is the issue happening when switching from the native ORM to LEAP? you may need to update the config to map the 'session_id' from 'id' to 'session_id' to match what the schema is expecting.
Hello, am pretty interested by your module but i got stopped at the first trial.am using kohana 3.2 am quite new on kohana, but i've used zend and doctrine for php and hibernate/jpa for java. i'am having session corrupt exception.i've found that the session schema included in the leap is a little different
after i run the default orm version the error is gone. Please advise
blacksensei