On 02/06/16 20:01, rverghese wrote:
> 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 (PH
On Thu, 2016-06-02 at 11:01 -0700, rverghese wrote:
> 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
> retu
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 us
