Switch from using execute_array to execute_for_fetch directly
authorPeter Rabbitson <ribasushi@cpan.org>
Sat, 10 Dec 2011 23:44:37 +0000 (00:44 +0100)
committerRafael Kitover <rkitover@cpan.org>
Tue, 14 Feb 2012 18:44:51 +0000 (13:44 -0500)
commit52cef7e30a43620553dc38ce52a10946b76a814c
tree3a7c8547b906c3adec5eb8d56c7052b4f549e105
parent6d5679b24ddc274203df7399901f33c8eb9355f1
Switch from using execute_array to execute_for_fetch directly

This saves us from pivoting our data into column slices, which execute_array
promptly turns back into our initial row-based format to feed to
execute_for_fetch. Apart from the obvious speed gain, this saves a lot of
memory since it avoids 2 copies of the (possibly rather large) dataset
Changes
lib/DBIx/Class/Storage/DBI.pm
lib/DBIx/Class/Storage/DBI/Oracle/Generic.pm
lib/DBIx/Class/Storage/DBI/Replicated.pm
lib/DBIx/Class/Storage/DBI/Sybase/ASE.pm
t/100populate.t