We are looking to move from one large table to partitioned tables. Since the
inserts and updates are made to the master table and then inserted into the
appropriate partitioned table based on the trigger rules, the affected_rows
returned to the client (PHP in this case) is always 0. We have been using
the affected_rows to check various things on the client end. Is there an
alternative to check for rows affected with partitioned tables? Seems like a
pretty big missing feature.
Thanks
RV
--
View this message in context:
http://postgresql.nabble.com/Partitioned-tables-do-not-return-affected-row-counts-to-client-tp5906112.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
