Re: Column privileges and Hibernate (SOLVED)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, PostgreSQL <pgsql-general(at)postgresql(dot)org>
Subject: Re: Column privileges and Hibernate (SOLVED)
Date: 2010-01-06 06:06:57
Message-ID: 25628.1262758017@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> This begs the question of if this is something PG should just allow
> rather than denying the update.

AFAICT, throwing a permissions error for "UPDATE SET foo = foo" is
required by the SQL standard. There's nothing in there about "it's
okay depending on what you assign to it".

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Yan Cheng Cheok 2010-01-06 06:17:17 Re: PostgreSQL Write Performance
Previous Message Ahmad Rumman 2010-01-06 05:22:34 incomplete startup packet