> Ok, so of course, a few more minutes of searching/reading/googling,
> and I found the answer to my own question:
>
> currval()/nextval()
I am not sure what the best practice is for adding records to both a "parent" and "child" table.
However, examples in the postgresql documentation demonstrate the use a view that joins the parent
and child tables.
Rules are used to propagate insert/update/delete statements on the view to the actual parent/child
tables. In addition to this, inserts to the view can also be redirected using triggers.
Once this is setup, I would expect that it would simplify your procedural code.
See:
http://www.postgresql.org/docs/8.1/interactive/rules.html
I would be interested in seeing if there is a way to preform operations like this (without views)
with just one Sql statement.
Regards,
Richard Broersma Jr.
