create table tomcat_sessions ( session_id varchar(100) not null primary key, [...]
The DBA says that setting a primary key forces an index of this field, and that the size could be a problem on the DB.
Yeah, 100 characters seems high for a PK. Well, will Tomcat leave old sessions in the database, or will it remove the ones that time-out or are otherwise invalidated? If Tomcat will remove the old ones, than neither your tables nor your indexes will grow very big. This might make your DBA happier...
As far as I understand it, the size of the session_id in tomcat is 32bits. So, a varchar(32) should be enough.
I suppose this is a Tomcat-only solution, but it's possible that the session id format might change in the future or from servlet container vendor to vendor. I'd recommend using the wider higher session_id field.
-chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
