On Wed, 30 Aug 2000 [EMAIL PROTECTED] wrote:
> Short Description
> referential integrity requires write permission to a table which only needs to be
>read
Yes, this is a known problem.
> And, why is the trigger trying to select WITH UPDATE? (locking?)
Yes, if you don't grab a row lock, anothe
[EMAIL PROTECTED] writes:
> a transaction from psql shows referential integrity statements in the
> output, but a transaction from a client using libpq does not; they are
> both using the same backend, PGDEBUG=2:
I think you are misinterpreting what you see. The additional queries
needed for RI
"Barnes, Sandy (Sandra)" <[EMAIL PROTECTED]> writes:
> Platform: PostgreSQL 7.0.2 on RedHat6.2 Linux
> Test: Testing the creation of large objects. I was putting the large
> objects into a database table but this
>test program recreates the error for me without having to do that.
> Pr
Chris Green ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Page 13 of tutorial has a typo I believe
Long Description
the Cartesian product of domains.
such that V1 (is a member of) D1, V1 (is a member of) D1, ... Vk (is
Dave E Martin ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
misleading (or perhaps confusing) error messages
Long Description
When an error is generated as the result of a trigger (or other indirect action) it
would be helpf
