| From: | "Igor Neyman" <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | "Gregg Jaskiewicz" <gryzman(at)gmail(dot)com> |
| Cc: | Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Rules going away |
| Date: | 2011-09-30 12:34:55 |
| Message-ID: | F4C27E77F7A33E4CA98C19A9DC6722A20825359A@EXCHANGE.corp.perceptron.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> -----Original Message-----
> From: Gregg Jaskiewicz [mailto:gryzman(at)gmail(dot)com]
> Sent: Friday, September 30, 2011 5:18 AM
> To: Igor Neyman
> Cc: Ondrej Ivanič; pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Rules going away
>
> speaking of DO INSTEAD, for insert/update case. Try using RETURNING
> with that and rules ;) Good luck
Well, I designed it for specific case.
And in my application I had no need for RETURNING clause.
That's why I'm saying, it works perfectly for me, but I'm not trying to generalize, like those who say "Rules are evil and don't ever use them".
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregg Jaskiewicz | 2011-09-30 12:40:51 | Re: Rules going away |
| Previous Message | hamann.w | 2011-09-30 12:22:27 | how to improve this similarity query? |