On Sun, 14 Oct 2001, Stuart wrote:
> Then a destination table set up with a field referencing areas.
> Currently postgres appears not to support reference contraints checking
> through inherited tables. �Nor does it appear to support subselects in check
> constraints. �It would be nice to allow reference checking through the
> inherited tables so destination.area_id would be valid for any country,
> state, or city area_id entered.
This isn't currently supported, and probably isn't going to be supported
for a version or two at least. There are some problems in the current
inheritance scheme (for example, IIRC your primary key is also not
inherited, and even if you define one on the child it won't stop you from
having duplicates between the tables) and this is one of them. The work
to do this isn't so huge, but there are some issues about inheriting the
triggers that would need to be sat down and thought about.
