Hm,
Thanks again for helping out.
I think it would be hard to live without the WHERE statemement in my
case, since I will have a steady flow of inserts and need to have a
partition ready when time passes a partition boundary. I would have to
update the rule at the exact millisecond, wouldn't I?
I
I tried using rules instead. I did something very similar to this:
CREATE RULE measurement_insert_y2006m02 AS
ON INSERT TO measurement WHERE
( logdate >= DATE '2006-02-01' AND logdate < DATE '2006-03-01' )
DO INSTEAD
INSERT INTO measurement_y2006m02 VALUES (NEW.*);
...
CREATE RULE measureme
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
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 caus
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 caus
