Re: getting the number of affected rows

hi,

On Wed, Oct 18, 2006 at 09:54:25PM -0600, Kevin Rosenberg wrote:

> > i can write a patch with the proposed changes for postgresql and mysql,
> > (and perhaps sqlite2/3).
> 
> Very good. For mysql, it's a one line addition (as above). What do you
> think about adding support ODBC and Oracle in addition to the backends
> you mentioned?

from looking at the code it seems that the odbc backend already
supports this, i will try it tomorrow.

with oracle, it looks like one can use oci-attr-get to get the
+oci-attr-row-count+ of the statement handle.
i can add that to my patch, but cannot easily test it as i don't
have access to an oracle database.

> Also, additions would need to be made to the test suite to verify
> proper working of this over time. The update to the documentation
> would be quite simple.
> 
> I realize this task may seem larger than you originally thought. You
> might prefer to use one of the alternative approaches above rather
> than working on a robust addition to CLSQL.

unfortunately, with postgresql you need access to the result object
which is only available inside database-execute-command and i don't
really like the table locking approach.

also, i'd be glad to help improve clsql :)

bye,
hans.