I don't think I am crazy and the user who showed me the problem exists - but
damn it neither he or I cannot duplicate the problem. The only thing that
changed is each of us has logged out of our session and logged back in.
The only thing that could have happened is that sometime in the past the
Joel Krajden <[EMAIL PROTECTED]> writes:
> But if I create the tables as a mortal user or create them as postgres
> but in the schema of user joelk and grant all to user joelk, I can
> insert data without the foreign key constraint being respected. Now if
> I drop the foreign key constraint and rec
Hi Tom,
Ok. You are right but I am not crazy (yet).
If I create the tables and indexes as user postgres it works like a charm.
But if I create the tables as a mortal user or create them as postgres but in
the schema of user joelk and grant all to user joelk, I can insert data
without the foreign
Joel Krajden <[EMAIL PROTECTED]> writes:
> If the indexes are created in fis_index, the foreign key constraints in the
> user table are ignored on insert and update.
Works for me...
$ mkdir /tmp/fis
$ mkdir /tmp/fis_index
$ psql regression
...
regression=# create tablespace fis location '/tmp/fi
I have two tablespaces: fis (default) and fis_index. The users are required to
create the tables in fis and the indexes if fis_index.
If the indexes are created in fis_index, the foreign key constraints in the
user table are ignored on insert and update.
The constraints work properly if the ind
