# Mysql DBD and DBI -- affected\_rows

**URL:** <https://rubytalk.org/t/mysql-dbd-and-dbi-affected-rows/40470>\
**Category:** ruby-talk\
**Created:** [7 September 2007 19:20 UTC](https://rubytalk.org/t/mysql-dbd-and-dbi-affected-rows/40470 "2007-09-07T19:20:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Unknown](https://avatars.discourse-cdn.com/v4/letter/u/4bbf92/32.png) [@Unknown](https://rubytalk.org/u/Unknown)\
**Post date:** [7 September 2007 19:20 UTC](https://rubytalk.org/t/mysql-dbd-and-dbi-affected-rows/40470/1 "2007-09-07T19:20:12Z")

</div>

This is my first post on c.l.ruby. So, bear with me if this has been  
discussed before. I have been writing a few classes in ruby based on DBI  
(version 0.1.0). I have only used Mysql driver so far. I have a few  
questions related to DBI.

1) The DBI StatementHandle class seems to be encapsulating a cursor. Or is  
it just me? For example, there is no way to repeatedly use a StatementHandle  
object with different SQL statements.

2) There is no way to get affected\_rows on a queries (e.g. update, delete,  
etc.) that don't return results. There is a affected\_rows on DatabaseHandle  
but not on StatementHandle.

3) There is a StatementHandle#fetch\_array method, but no  
StatementHandle#bind\_array method. bind\_array method would be useful when  
inserting/updating more than one row at a time.

These are really not questions, but I am just trying to find out if I missed  
something.

-Venkat