Ren-Shan Luoh wrote: > Hi, > > Recently I'm installing RT 3.6.5 from FreeBSD ports. > The newly installed system can not keep data in the MySQL session store, > but it works normally with the File session store. > It looks like the same problem encountered by Matthew Seaman mentioned in > http://lists.bestpractical.com/pipermail/rt-users/2007-September/047788.html.
The fix I discovered on this list was: ALTER TABLE sessions MODIFY a_session longblob ; See: http://lists.bestpractical.com/pipermail/rt-users/2008-January/049583.html > When a new user connect to the system, > it creates a new, empty, abnormally long (103 bytes rather than 56 bytes) > record in the 'sessions' table. > When being 'thawed' by Storable, it only returns 'undef', not a hash > with a _session_id. It's possible this is an effect due to using utf8 as the default character set, which uses three bytes per character in certain circumstances. Cheers, Matthew -- Dr Matthew Seaman The Bunker, Ash Radar Station PGP: 0x60AE908C on servers Marshborough Rd Tel: +44 1304 814890 Sandwich Fax: +44 1304 814899 Kent, CT13 0PL, UK
signature.asc
Description: OpenPGP digital signature
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
