> Delete a row (3 nodes), deletes: 3, inserts: 3 (NOT OK?) > > Why is it reporting inserts for a delete action?
That's a good question with a complicated answer. The short version is that Bucardo doesn't know how many rows were actually inserted, so it defaults to the total possible rows. What actually happens is a COPY, not an insert. While Postgres does report back the number of affected rows (as of 8.3 IIRC), a copy is done via $dbh, not a $sth. So, even though DBD::Pg could grab the rows via PQcmdTuples, there is no clean place to stick it as DBI only defines $sth->rows. -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
signature.asc
Description: Digital signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
