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 fail if you exceeded it. (The variable is called max_allowed_packet, I believe.) If you have RaiseError on or you check the return value of the insert, you should be able to see it failing. > >Storage of attributes in database columns should handle concurrency > >better than anything using Storable because the locking and data > >transfer will be more efficient. > > I mean the Storable used by A::S to serialize the data. So am I. Because Apache::Session reads and writes the entire session every time, it is transferring much more data than a more granular approach with a normal table and updating separate columns. If it's in multiple tables, it gets even better, since individual parts can be locked separately (in a database that supports row-level locking, like MySQL InnoDB). > Sorry I can't create a test case because I don't really know what causes > this. Try writing a really large chunk of data to a session and see what happens. - Perrin
