Understood, was just wondering if there is a way to cause the child table insert results to be returned to the ORM/Application instead of the master/base table insert
Insert into the child table directly based on the partition rules.
JD
I would think the ORM (as yet undefined) would want to think in terms of the parent table and not know about the physical schema details. Can the client not be written to check only for errors vs checking for non-zero inserts?
That was our first suggestion, they don;t want to make any app changes
I highly suspect this is a problem with trigger function design, constraint conflict or a bad insert statement, but since no details have been provided, it cannot be resolved.
IOW, all they said was "It don't work", but they have not provided proof.
--
Melvin Davidson I reserve the right to fantasize. Whether or not you wish to share my fantasy is entirely up to you.