I respectfully request feedback for the following potential DBI array
insert solution.
PART 1
Add two new hash array attributes for the connect() and prepare()
methods called 'insertcount' and 'insertsize'. The 'insertcount'
attribute tells the execute() method to 'cache' a number of rows before
performing an array insert. The 'insertsize' attribute tells the
execute() method to not exceed the specified 'cache' size. The
'insertsize' attribute should override the 'insertcount' attribute. If
these two attributes aren't set then, for backwards compatibility, the
existing DBI v1.14 behavior should prevail (the default for
'insertcount' should be 1). If the statement being prepared is not an
insert and the attributes were set via:
. connect(), then they should be ignored
. prepare(), then an error should be raised
PART 2
Add a new method called execflush() that allows the programmer to
control the DBI's behavior on commit or disconnect. One could possibly
argue that
the DBI could 'sense' pending rows prior to a commit or disconnect.
Thanks,
--
Jeff Holt
Chief Scientist, Hotsos LLC
mailto:[EMAIL PROTECTED]
+1.817.821.9553 tel
+1.413.480.7346 fax
http://www.hotsos.com
