[EMAIL PROTECTED] wrote:
Perrin Harkins writes:
On Wed, 2005-11-30 at 15:23 +1000, Badai Aqrandista wrote:
I am using MySQL 4.1 on debian sarge. The type of the field that hold the
session data is 'longtext'.
That holds a very large amount of data. You can't be overflowing that.
Patrick Mich
On Thu, 2005-12-01 at 09:20 +1000, Badai Aqrandista wrote:
> > > Patrick Michaud pointed me off the list that i
> > > should also bump max_packet_size up.
> >
> >Probably, but that will not make you lose data.
>
> But I guess in MySQL it does. Can anyone confirm this?
I would expect the insert to
> Patrick Michaud pointed me off the list that i
> should also bump max_packet_size up.
Probably, but that will not make you lose data.
But I guess in MySQL it does. Can anyone confirm this?
> Yes, that's why I am using Storable hooks to only serialize as small
> information as possible.
S
Perrin Harkins writes:
> On Wed, 2005-11-30 at 15:23 +1000, Badai Aqrandista wrote:
> > I am using MySQL 4.1 on debian sarge. The type of the field that hold the
> > session data is 'longtext'.
>
> That holds a very large amount of data. You can't be overflowing that.
>
> > Patrick Michaud poin
On Wed, 2005-11-30 at 07:33 -0500, [EMAIL PROTECTED] wrote:
> I do believe setting the LongReadLen will fix your problem
That only applies to Oracle, and they are using MySQL.
When LongReadLen is the problem, you don't just lose some data from a
session -- the entire session for that user becomes
On Nov 30, 2005, at 12:30 AM, Perrin Harkins wrote:
It certainly can be a scoping issue, but it could also be a locking
issue. Without seeing a test case that causes it, it's pretty hard to
guess.
I'd suggest running data dumper and storing each iteration of a
'session' variable to a differ
On Wed, 2005-11-30 at 15:23 +1000, Badai Aqrandista wrote:
> I am using MySQL 4.1 on debian sarge. The type of the field that hold the
> session data is 'longtext'.
That holds a very large amount of data. You can't be overflowing that.
> Patrick Michaud pointed me off the list that i
> should
Hi Perrin,
What database are you using? I thought the default data types for most
of them would hold a very large amount of data before having trouble. I
suspect you are having locking problems or session data is not being
written because the session object doesn't go out of scope.
I am usin
On Wed, 2005-11-30 at 14:29 +1000, Badai Aqrandista wrote:
> I am experiencing intermittently missing session data. After weeks of
> investigation, we suspect the size of the data we put in the session as the
> culprit: it is too big.
What database are you using? I thought the default data type
Hi All,
I am experiencing intermittently missing session data. After weeks of
investigation, we suspect the size of the data we put in the session as the
culprit: it is too big. So I am trying to fix it by adding Storable hooks
for objects stored in the session to create smaller serialized dat
10 matches
Mail list logo
