On 17 Jun 2009, at 21:34, Stuart Watt wrote:
Since Session::Store::DBI can be set to use its own connection, I
thought that might resolve it. Not completely, unfortunately, and
now the error is due to the recommended use of a text column for
the data. It seems the DBI+DBD::ODBC likes to
On 18-Jun-09, at 4:01 AM, Tomas Doran wrote:
Any session data at all? Can you be more specific - I'd guess that
this should only hit you if the length is small, or if your sessions
get large.
No, the sessions were tiny, more or less all they held was the id for
which project the user
I don't know if anyone else has hit these problems, and I am working on
them, but there appear to be a set of significant issues around the DBI
and DBIC session stores using Microsoft SQL Server as the back-end.
These are mostly related to the fact that MSSQL only allows one active
statement
