[Bug 495] Changed - scripts/database/*.sql field length error (sid)
bugs@bugs.horde.org
bugs@bugs.horde.org
Thu, 12 Oct 2000 23:39:30 -0300
http://bugs.horde.org/show_bug.cgi?id=495
*** shadow/495 Thu Oct 12 17:56:30 2000
--- shadow/495.tmp.9737 Thu Oct 12 23:39:30 2000
***************
*** 9,15 ****
Priority: P2
Component: IMP
Area: BUILD
! AssignedTo: chuck@horde.org
ReportedBy: percy@py.dhs.org
URL:
Summary: scripts/database/*.sql field length error (sid)
--- 9,15 ----
Priority: P2
Component: IMP
Area: BUILD
! AssignedTo: bjn@horde.org
ReportedBy: percy@py.dhs.org
URL:
Summary: scripts/database/*.sql field length error (sid)
***************
*** 20,22 ****
--- 20,30 ----
varchar(34) or more. It must be either the leading "1_" has mistakenly got into
the SQL query or the varchar(32) should be changed somehow. BTW, the
imp/docs/DATABASE says it's a varchar(32).
+
+ ------- Additional Comments From bjn@horde.org 10/12/00 23:39 -------
+ As far as I'm aware, session IDs like "N_xxxxxxx...", in other words, 32
+ characters with an "N_" prefix, are only generated when PHPLIB is configured to
+ use shared memory... in which case, they don't need to be stored in the SQL
+ database, and the 32-char limit won't be a problem. I don't believe this is a
+ bug... are you certain that what you're seeing has actually caused something to
+ break? If so, please give more details.