I think that if you use a RULE instead of a TRIGGER to redirect the write, it should return the proper number of rows inserted in the child table. //Magnus Mattias.Arbin@xxxxxxxxxxxxxxx wrote: > Scott, > You're right, of course. I meant, is there a way to make Postgres return > the number of rows inserted to any child table _via_ the master table + > trigger function? > I have not been able to find a way to tell Hibernate to ignore the > returned number of rows, unless I insert via a custom insert statement. > /Mattias > > -----Original Message----- > From: Scott Marlowe [mailto:scott.marlowe@xxxxxxxxx] > Sent: den 5 juni 2008 02:01 > To: Arbin Mattias > Cc: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: [GENERAL] Insert into master table ->" 0 rows affected" -> > Hibernate problems > > On Tue, Jun 3, 2008 at 7:38 AM, <Mattias.Arbin@xxxxxxxxxxxxxxx> wrote: >> I have implemented partitioning using inheritance following the >> proposed solution here (using trigger): >> http://www.postgresql.org/docs/8.3/interactive/ddl-partitioning.html >> >> My problem is that when my Hibernate application inserts to the master > >> table, postgres returns "0 rows affected", which causes Hibernate to >> throw an exception since it expects the returned row count to be equal > >> to the number of rows inserted. >> >> Is there a solution to this, i.e. to get Postgres to return the >> correct number of rows inserted to the master table? > > PostgreSQL IS reporting the correct number of rows inserted into the > master table. 0. > > There's some setting in hibernate that will tell it to ignore that > returned number of rows, but I can't remember it right now. >
