On Mon, Jun 05, 2000 at 11:46:51AM -0700, John McNally wrote:
> > However as it happens the mm.mysql JDBC drivers for MySQL read
> > the whole resultset into memory immediately,
>
> This does not seem to be a very good design for the driver, but I shouldn't
> talk I've never written one. Anyone know how the other db drivers handle
> the resultset?
No, I've never written one either, but I was surprised to discover this,
and I wouldn't be surprised if other drivers have ResultSet actually
talk to the DB. This was the behaviour I expected to find in mm.mysql
when I had to find out for a different reason.
> Please feel free to add any standard SQL clauses to Query and related
> classes. Group By could be one for example. Note that if I have a fairly
> complicated Where clause (IN is generally means complex enough), I just add
> the entire clause as a Custom criteria. I know the syntax is messy, but it
> comes in handy once in a while.
Sure - and I was going to do my IN clauses with Custom, but decided that
adding an IN clause with an array/vector as the criteria was general
enough to be useful as a specific capability of Criteria/SqlExpression.
My patch to do this is ready, but now I'm thinking I'll hold off and
think about this other stuff that's come up.
> I am not sure how well supported the LIMIT clause is supported, does Oracle
> support it?
(just read Stephen's email) Okay, so this would need to be done through
the database adaptor as well. Still if I'm going to look at this for
ignoreCase, might as well throw this in too? (After all if we_are_ going
to drop OPaL, it seems worthwhile to throw some more goodies into
BasePeer).
--
Sean Legassick
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
