From 600fae75ef32d5b52710e0cace9683491bed26bc Mon Sep 17 00:00:00 2001 From: jbjohnso Date: Sat, 28 Nov 2009 00:52:10 +0000 Subject: [PATCH] -Raise nodes at a time in the setNodesAttribs to 999 to account for the re-execute strategy allowing it to be that high git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@4684 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd --- perl-xCAT/xCAT/Table.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/perl-xCAT/xCAT/Table.pm b/perl-xCAT/xCAT/Table.pm index 217aadd8c..a277ac21b 100644 --- a/perl-xCAT/xCAT/Table.pm +++ b/perl-xCAT/xCAT/Table.pm @@ -1543,7 +1543,7 @@ sub setNodesAttribs { }; @orderedcols = keys %cols; #pick a specific column ordering explicitly to assure consistency use Data::Dumper; - my $nodesatatime = int(1/(1/999+(scalar @orderedcols)/999)); #the update case statement will consume '?' of which we are allowed 999 in the most restricted DB we support + my $nodesatatime = 999; #the update case statement will consume '?' of which we are allowed 999 in the most restricted DB we support #ostensibly, we could do 999 at a time for the select statement, and subsequently limit the update aggregation only #to get fewer sql statements, but the code is probably more complex than most people want to read #at the moment anyway