John Armstrong wrote:
>
> On this thread, I am seeing a lot of things in the archives hinting
> at issues and problems with Apache::Session ( DBI usage ) and high
> end DB's like Oracle and SyBase.
>
> What sort of success is anyone seeing using Oracle/SyBase with
> Apache::Session. Apache::Session in a DBI context is crucial to our
> development effort so that is a huge factor.
>
> We are also looking at using Mason but I don't see any problems with
> that right offhand.
I recommend using mySQL as the datastore for Apache::Session. You may
have problems with Oracle, although I haven't checked lately. You will
have problems with Sybase, although fixes are available.
Apache::Session comes with the source code.
MySQL is great for Apache::Session because everything that
Apache::Session does is atomic: it doesn't need transactions at the
database level. MySQL inserts are very fast because it doesn't (cannot)
check referential integrity and the like. Also MySQL's TEXT column type
is much easier to use than the Oracle *LOB datatypes, at least when DBI
is the interface.
Of course you can use mySQL for sessions alongside the Oracle that you
use for business data.
-jwb