[Slashcode-development] mod_perl 2 and PostgreSQL revisited

[Ian K. <ik-...@th...>]

[I'm re-sending this from the correct address that I'm subscribed to the
list.  The moderators can discard the earlier copy from a day and a half
ago which was held by Mailman.  Or if that one winds up on the list too,
sorry for the duplication.]

Slashcode developers -

I'd like to port and contribute the patches for mod_perl 2 and PostgreSQL
compatibility for Slash.  I've done some analysis to scope out the problem.
But I realize that it wouldn't be useful to proceed beyond this point
without contacting you.

Here's a page describing what I've done so far and my initial idea of
how to proceed.

  "SlashCode compatibility with mod_perl 2 and PostgreSQL: Scoping the Problem"
  http://www.kluft.com/~ikluft/opensource/slash/

Whether or not to continue on this really depends on determining if you're
interested, and gaining your support.  It's a lot of work but this analysis
shows what needs to be done.  It would only be worthwhile if I know that
the effort has a reasonable chance (pending your usual code submission
procedures, of course) of going into the code base.

As others have pointed out before, one of the big things for PostgreSQL
support is to split up Slash/DB/MySQL/MySQL.pm.  80% of the functions
are not MySQL specific at all, and can be moved to a common parent class.
Another 16% of the functions will need some database-specific code moved
to new database-specific functions before the rest of that code can also
go to the common parent class.  (Some would have worked in PostgreSQL
but not in Oracle, so I included them here too.)  Only 8 functions are
completely MySQL specific in there.  Then some documentation will be
needed to show how to make future code portable among supported databases.

Should I proceed?  Obviously only if the Slash developers are interested,
and would be willing to go along with portability after it's in.  For
example, once the split is done, we can't have new non-MySQL stuff going
into MySQL.pm again.  While I think that's something you'd readily go
along with, I still have to ask because it's entirely up to you.