Chris Pizzi <[EMAIL PROTECTED]> writes:
> Creating a "select" rule on a table should fail if the table is
> referenced by foreign key constraints.
Creating a "select" rule on a table should fail, period. It does not
because we left that feature in for backwards compatibility with ancient
pg_dum
POSTGRESQL BUG REPORT TEMPLATE
Your name : Chris Pizzi
Your email address : [EMAIL PROTEC
> Erkki Seppala <[EMAIL PROTECTED]> writes:
>> The following session crashes with 6.5.3 (with i386 debian woody, 6.5.3-13):
> Hmm. In current sources I get
> regression=# update data set data=5 where data=5;
> ERROR: ExecEvalExpr: unknown expression type 108
> which is better than a crash, bu
Erkki Seppala <[EMAIL PROTECTED]> writes:
> The following session crashes with 6.5.3 (with i386 debian woody, 6.5.3-13):
Hmm. In current sources I get
regression=# update data set data=5 where data=5;
ERROR: ExecEvalExpr: unknown expression type 108
which is better than a crash, but not by mu
What I'm trying to do is to deny people from touching stuff they don't
'own'. I have a table which maps postgresql user-names to user-ids. Here is
a shorter version of my problem. It could be implemented differently, but
the point is that it crashes.. And only with update.
The following session c
