Michael Neumann wrote:
(...)
> Well, I think Ruby/DBI is not the fastest. It parses (and splits)
each
> SQL statement, then joins it back into a string, even if you don't
use
> '?' parameter markers. This should be delayed and omitted if no
> parameters were given. Not sure whether this is the reason for the
slowness.
>

This may be a dumb question, but why does ruby/dbi do that?  For
databases that don't support precompiled statements and binding
parameters?

-Charlie