[Cgi-session-user] RT#224 and CGI::Session::PureSQL

[Ron S. <ro...@sa...>]

Hi Mark

Examining CGI::Session::PureSQL I see it starts with:
use base qw(
    CGI::Session
    CGI::Session::ID::MD5
	CGI::Session::Serialize::SQLAbstract
);
but there is no package CGI::Session::ID::MD5, but there is a
CGI::Session::ID::md5 (lc MD5). So, CGI::Session::PureSQL is not really
production-ready, right :-)?

Also, I had to delete t/01_serialize_sql_abstract.t to make progress.

And what's this stuff about Indiana time? Even here in Australia we know
there's no one dead or alive /really/ living in Indiana, right :-)))?

Should I work on CGI::Session::PureSQL (hint: No) or should I pursue the
idea of getting the DBI-oriented code to accept specific names for
columns, not just for MySQL, but Pg, and (gasp) my own code:
o CGI::Session::Driver::odbc
o CGI::Session::Driver::oracle

I can see I might add $IdName and $DataName say alongside $TableName in
CGI::Session::Driver::DBI and to have that package's descendents also
have local vars of the same name and to default the values from the
parent. That way, users could set the 2 col names the same way they can
set the table name. What do you think?
-- 
Ron Savage
ro...@sa...
http://savage.net.au/index.html