Re: [Slashcode-development] mod_perl 2 and PostgreSQL revisited

[Shane <sh...@lo...>]

On Sep 5, 2004, at 5:59 PM, Ian Kluft wrote:

> 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.

Smart man :)

>
> 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.

Understandable.

>
> 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.

I've always wondered about that. Even though there is Slash::DB::* most 
everything seems to be  Slash::DB::MySQL.


> Should I proceed?

While I'm no official slash-dev, I vote hell yeah do it. It seems to 
make sense to me to separate as much generic db-code out and create the 
unique db code in each. The more db's slash will work with out of the 
box, the more users of the software. And the more users, the more 
add-ons developed.

At-least, that's how it'd work in my fairy-tale world... :)

  Shane

PS - There's another benefit of this. Once it'd happen, it would be far 
easier to release plugins that'll work with add'l sql backends. Yes, 
you'd think that'd be obvious, but the idea just popped into my head :)