[ic] Cluster and/or load balancing question

[interchange-users@icdevgroup.org (Dan Browning)]

At 10:58 AM 7/16/2002 -0600, you wrote:
>Quoting Dan Browning <dbml@kavod.com>:
>
> > At 11:02 AM 7/13/2002 -0700, you wrote:
> > >At 11:41 AM 7/13/2002 -0600, you wrote:
> > >>Quoting Dan Browning <dbml@kavod.com>:
> > >>Again the only thing would be to publish how to use MySQL for the 
> sessions
> > as
> > >>opposed to the default methods.
> > >
> > >Consider it done (once I get back from Kentucky, that is).
> >
> > A very humble beginning for the "Interchange Clustering HOWTO" is up at:
> >
> > http://www.icdevgroup.org/~danb/
> >
> > Please offer feedback (including how setting up MySQL sessions goes for
> > you).
> >
>
>
>G'Day Dan,
>
>I found a few little things that may need to be clarified a bit...
>You definitions should read more like this:
>
>
>Variable        MYSQL_SESSIONS_YES      1
>Variable        SESSION_DSN             dbi:mysql:sessionfiles:mysql_hostname
>Variable        SESSION_USER             dbi:mysql:sessionfiles:mysql_hostname
>Variable        SESSION_PASS             dbi:mysql:sessionfiles:mysql_hostname

I think that should really just be the plain user name and password, not 
the DSN.

>ifdef MYSQL_SESSIONS_YES
>Message Enabling MySQL-based sessions...
>SessionType DBI
>Database  session  session.txt  __SESSION_DSN__
>Database  session  USER         __SESSION_USER__
>Database  session  PASS         __SESSION_PASS__
>Database  session  COLUMN_DEF   "code=varchar(64) NOT NULL PRIMARY KEY"
>Database  session  COLUMN_DEF   "session=blob"
>Database  session  COLUMN_DEF   "sessionlock=VARCHAR(64) DEFAULT ''"
>Database  session  COLUMN_DEF   "last_accessed=TIMESTAMP(14)"
>SessionDB   session
>Message ...Done
>endif
>
>It has always been my understanding, if a field is defined as a primary key,
>then it is indexed, so you don't need the index line. Also if the first column
>is named code, Interchange defaults to using it as the key, so you don't need
>that line either.

Too true -- it is updated now.  Thanks for the once-over,

+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Dan Browning, Kavod Technologies <db@kavod.com>
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Real programmers don't write in FORTRAN.  FORTRAN is for pipe stress
freaks and crystallography weenies.  FORTRAN is for wimp engineers who
wear white socks.