Hello,
this issue has been requested and its on the TODO-list. Since I really
need foreign key constraints on inherited tables, I have two solutions:
Adding some hackish RULES/TRIGGERS to my tables or implementing it
myself. It think the latter is better. However, I have no experience in
I tried to write a trigger using C++. This requires to include the
following header-files:
extern C {
#include postgres.h
#include executor/spi.h
#include commands/trigger.h
#include fmgr.h
}
Unfortunately some of the included headers define some structs and
functions where a few identifiers are
Tom Lane wrote:
That is most likely not going to work anyway, because the backend
operating environment is C not C++. If you dumb it down enough
--- no exceptions, no RTTI, no use of C++ library --- then it might
work, but at that point you're really coding in C anyway.
Writing normal
