do not use TRUNCATE when refreshing reporter.materialized_simple_record
authorgmc <gmc@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Wed, 10 Nov 2010 13:31:09 +0000 (13:31 +0000)
committergmc <gmc@dcc99617-32d9-48b4-a31d-7c20da2025e4>
Wed, 10 Nov 2010 13:31:09 +0000 (13:31 +0000)
commit3d6209fe76cc1bb633512a62165f9938c4debb13
tree245afde424f7e722f6c3987dde7ce1a7ca684f82
parent57f918024457c692f9d5629ac703f7349c5f81f2
do not use TRUNCATE when refreshing reporter.materialized_simple_record

Previous behavior would break Slony replication after doing a
bib load.  Since a deletion is slower than a truncate, if you're
not using Slony replication, you may prefer to truncate rmsr
prior to calling reporter.enable_materialized_simple_record_trigger.

Signed-off-by: Galen Charlton <gmc@esilibrary.com>
git-svn-id: svn://svn.open-ils.org/ILS/branches/rel_1_6_0@18681 dcc99617-32d9-48b4-a31d-7c20da2025e4
Open-ILS/src/sql/Pg/reporter-schema.sql