On Sunday 15 November 2009 5:18:20 pm Tom Lane wrote:
> "Bob Pawley" writes:
> > Hope this elucidates you?
>
> No, it's all handwaving. In particular, showing only a fragment from
> a case that does work as you expect doesn't illuminate what's not
> working. Please show the whole table definiti
"Bob Pawley" writes:
> Hope this elucidates you?
No, it's all handwaving. In particular, showing only a fragment from
a case that does work as you expect doesn't illuminate what's not
working. Please show the whole table definition, the whole trigger,
and the specific case that's not doing wha
ever, when the serial column is
updated I get a return which includes pump1 and pump2 as well as the serial
column.
Hope this elucidates you?
Bob
- Original Message -
From: "Tom Lane"
To: "Bob Pawley"
Cc: "Postgresql"
Sent: Sunday, November 15, 2009 3
"Bob Pawley" writes:
> "PostgreSQL does not support specific column updates in triggers."
> I found this statement on a blog.
> Is there a workaround for this?
If you'd explain what you think that statement means, maybe we could
help you ...
regards, tom lane
--
Sent v
"PostgreSQL does not support specific column updates in triggers."
I found this statement on a blog.
Is there a workaround for this?
I've attempted using 'new' (refering to the specific column) without success.
Bob
