OK, then we should at least forbit making such things... Otherwise, it
seems to be smth like gotcha.
But look at this please:
"12) If is specified, then the is
evaluated for each row of T prior
invocation of any caused by the imminent or actual
deletion of any row of T."
Does Postgres work
The following bug has been logged online:
Bug reference: 2558
Logged by: Dror
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: win 2003
Description:initDB failed to run
Details:
On one of mine win 2003 machine ( on any other win2003 machi
The following bug has been logged online:
Bug reference: 2560
Logged by: PFudd
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: N/A
Description:Web page documentation hard to use
Details:
I'm trying to look up the SQL keyword 'in' using t
The following bug has been logged online:
Bug reference: 2561
Logged by: Brian Hurt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.01
Operating system: Documentation
Description:Manual is wrong: You can't grant a group to public
Details:
The manual page for
The following bug has been logged online:
Bug reference: 2559
Logged by: flash.xu
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: fc5
Description:why jdbc-driver AbstractJdbc2ResultSetMetaData.
getTableName(int column) return ""
Details:
Hi,I'm running Postgresql 7.3 in Debian Woody OS.After some time working properly, insert's statements related this error:referential integrity violation - key referenced from xxx not found in yyy
This error would be normal, if the key really doesn't exist, but the key exist.The insert's wo
Brian Hurt wrote:
> The manual page for grant here:
>
> http://www.postgresql.org/docs/8.1/interactive/sql-grant.html
>
> indicates that you can grant a group to public. The discussion of
> priveleges here:
>
> http://www.postgresql.org/docs/8.1/interactive/privileges.html
>
> indicates that
On Wed, 2 Aug 2006, Luiz Henrique wrote:
> Hi,
>
> I'm running Postgresql 7.3 in Debian Woody OS.
>
> After some time working properly, insert's statements related this error:
>
>
> referential integrity violation - key referenced from xxx not found in yyy
>
>
> This error would be norma
"Brian Hurt" <[EMAIL PROTECTED]> writes:
> The manual page for grant here:
> http://www.postgresql.org/docs/8.1/interactive/sql-grant.html
> indicates that you can grant a group to public. The discussion of
> priveleges here:
> http://www.postgresql.org/docs/8.1/interactive/privileges.html
> indic
On 8/2/06, Nikolay Samokhvalov <[EMAIL PROTECTED]> wrote:
Does Postgres work this way? In the case of 'delete from tbl;' we
have search condition>=TRUE for all rows. If we evaluate it *before*
any other operation, we should mark all rows to be deleted. I guess,
Postgres doesn't follow this logi
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> I don't understand how this can be called "not bug"... Please, help me
> understand it :-)
The situation is that the DELETE arrives at a row after the trigger has
already UPDATEd that row. You could make a reasonable case for throwing
an error i
11 matches
Mail list logo