Major Change: INSERT/UPDATE/DELETE queries will now return the logical number of tuples that get modified (rather than the physical). This is the way it's suppose to be. Restored support for TestReplicationSuite to verify this
Added test case to TestHStoreSiteSuite that verifies we execute queries in the right order when we do a broadcast update... I should really be writing my dissertation and not messing with this...
Fixes in how we handle the # of modified tuples for an INSERT/UPDATE/DELETE on a replicated table.
More fixes after the logic tuple correction for replicated tables. Moved the dependency ordering test for replicated table updates to TestSQLFeaturesSuite