httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Kew <n...@webthing.com>
Subject Re: Limitations of mod_dbd - single server per vhost
Date Wed, 22 Aug 2012 14:47:13 GMT
On Wed, 22 Aug 2012 09:21:16 -0400
"Mikhail T." <mi+thun@aldan.algebra.com> wrote:

> On 22.08.2012 07:24, Nick Kew wrote:
> > The implementation needs object persistence, of the kind we have
> > in the per-server configuration but not per-directory.  That was the
> > original design constraint.
> I'd say, my complaint was a little misunderstood. It is not, that I wish 
> to see separate DBD-configurations per location/directory, though it may 
> be a good thing too.

Yes, the discussion got sidetracked.  Probably my fault!

> Then RewriteMaps can then changed to operate thus:
> 
>     RewriteMap	first	"dbd:first:SELECT ...."
>     RewriteMap	second	"dbd:second:SELECT ...."

Indeed that would follow if we had multiple backends.  Indeed,
it could go further and capture multiple return fields, either
by name or in the manner of regexp backreferences.  This kind
of incremental advance happens when someone feels motivated to
hack it.

> I don't think, I'm the best person to implement this -- whoever 
> "quick-hacked" the dbd-maps in recently is, probably, better positioned 
> to do this ;-)

It wasn't actually very recent:
https://svn.eu.apache.org/viewvc?view=revision&revision=454683


> P.S. BTW, I fixed the FreeTDS/Sybase driver 
> <https://issues.apache.org/bugzilla/show_bug.cgi?id=53666> for APR/APU 
> somewhat -- it has been absolutely broken and unusable for years, no 
> kidding -- but don't see any movement on the ticket... Does anyone care?

To be fair, I think that driver carried some health warnings!
I think I've pointed a few people at the ODBC driver as an alternative.
Do you have a strong reason to use FreeTDS rather than ODBC?

One question here may be, does anyone have the platforms to test-drive
your patch?  It seems to do rather more than just fix a simple bug:
you've removed the untainting code which was part of protecting against
injection attacks.  Have you implemented prepared statements properly
for all backends?

It worked for its original users at the time it was written, but I guess
it's withered on the vine since then.  Maybe it's some stumbling on some
difference between the different FreeTDS backends: you might even be
the first person to report trying it with Sybase!

-- 
Nick Kew

Mime
View raw message