Author: mjevans
Date: Tue Oct 19 00:49:53 2010
New Revision: 14501

Modified:
   dbi/trunk/Changes
   dbi/trunk/lib/DBI/DBD.pm

Log:
Document dbd_st_execute return


Modified: dbi/trunk/Changes
==============================================================================
--- dbi/trunk/Changes   (original)
+++ dbi/trunk/Changes   Tue Oct 19 00:49:53 2010
@@ -8,6 +8,7 @@
 
 =head2 Changes in DBI 1.616 (svn r14486) 15th October 2010
 
+  Documented dbd_st_execute return (Martin J. Evans)
   Fixed spurious dbi_profile lines written to the log when
     profiling is enabled and a trace flag, like SQL, is used.
   Fixed to recognize SQL::Statement errors even if instantiated

Modified: dbi/trunk/lib/DBI/DBD.pm
==============================================================================
--- dbi/trunk/lib/DBI/DBD.pm    (original)
+++ dbi/trunk/lib/DBI/DBD.pm    Tue Oct 19 00:49:53 2010
@@ -2308,6 +2308,10 @@
 
   int dbd_st_execute(SV* sth, imp_sth_t* imp_sth);
 
+C<dbd_st_execute> should return -2 for any error, -1 if the number of
+rows affected is unknown else it should be the number of affected
+(updated, inserted) rows.
+
 Note that you must be aware a statement may be executed repeatedly.
 Also, you should not expect that C<finish()> will be called between two
 executions, so you might need code, like the following, near the start

Reply via email to