-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Simply name the table constraints yourself with a descriptive name, so you
>> always know exactly what is going on:
> And then I keep a list of all the constraint names and scan the error
> message for it?
Don't keep a list: just come up with a
"M.D.G. Lange" <[EMAIL PROTECTED]> writes:
> No matter what ON DELETE constraint I created, the system will not allow
> me to create a foreign key, as pg_shadow is a system catalog.
We do not support foreign keys (or indeed triggers of any kind) on
system catalogs. I don't foresee that happening
The problem is, that a SELECT * FROM foobar; takes ages (roughly 3
minutes) to return the first row. I played around with the fetchSize()
to disable the result set caching in the Java program first (before I
tried psql) but that did not change anything.
Hello,
Yours seemed
Dear list,
Upon designing our application we thought that the following setup would
be a good idea to implement security:
Using the pg_shadow table as it is:
| pg_shadow |
+-+
| usename |
| usesysid|
| usecreatedb |
| usesuper|
| usecatupd |
| passwd |
| valunt
