[freeside-commits] branch master updated. 246670205503b6bcd91130325d2d9050fb7b74e5

[Ivan]

The branch, master has been updated
       via  246670205503b6bcd91130325d2d9050fb7b74e5 (commit)
       via  4feff1c4a6a53f879d9c0dfeedfdd6a70bdf1401 (commit)
      from  9bc9485d65cb202cc8df6ed37602664aafb80ea1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 246670205503b6bcd91130325d2d9050fb7b74e5
Merge: 4feff1c 9bc9485
Author: Ivan Kohler <ivan at freeside.biz>
Date:   Sun May 6 01:04:18 2012 -0700

    Merge branch 'master' of git.freeside.biz:/home/git/freeside


commit 4feff1c4a6a53f879d9c0dfeedfdd6a70bdf1401
Author: Ivan Kohler <ivan at freeside.biz>
Date:   Sun May 6 01:04:01 2012 -0700

    some ideas on speeding up the cust_main upgrade for big databases

diff --git a/FS/FS/cust_main.pm b/FS/FS/cust_main.pm
index cba28bc..49b76ce 100644
--- a/FS/FS/cust_main.pm
+++ b/FS/FS/cust_main.pm
@@ -5086,6 +5086,16 @@ sub process_censustract_update {
   return;
 }
 
+#starting to take quite a while for big dbs
+# - seq scan of h_cust_main (yuck), but not going to index paycvv, so
+# - seq scan of cust_main on signupdate... index signupdate?  will that help?
+# - seq scan of cust_main on paydate... index on substrings?  maybe set an
+#    upgrade journal flag now that we have that, yyyy-m-dd paydates are ancient
+# - seq scan of cust_main on payinfo.. certainly not going toi ndex that...
+#    upgrade journal again?  this is also an ancient problem
+# - otaker upgrade?  journal and call it good?  (double check to make sure
+#    we're not still setting otaker here)
+
 sub _upgrade_data { #class method
   my ($class, %opts) = @_;
 

-----------------------------------------------------------------------

Summary of changes:
 FS/FS/cust_main.pm |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)