em is that even when queries work, for the future potential
breakage the fall-back to ORM should always work... and it doesn't.
On Wed, Sep 11, 2013 at 12:57 AM, Alban Hertroys wrote:
> On 11 September 2013 07:53, Sergey Shelukhin wrote:
>
>> The query suffers from the auto-lo
#x27;ll
have to work around it... Thanks.
On Tue, Sep 10, 2013 at 9:39 PM, Scott Marlowe wrote:
> On Tue, Sep 10, 2013 at 7:02 PM, Sergey Shelukhin
> wrote:
> > Hi.
> > Is there any way to make postgres not abort the transaction on failed
> > select?
> >
> >
would intuitively expect from select in this case
(which is not a constraint check failure, of course; but it's even less
"dangerous" to ignore, in spirit).
On Tue, Sep 10, 2013 at 7:03 PM, David Johnston wrote:
> Sergey Shelukhin wrote
> > Hi.
> > Is there any way t
Hi.
Is there any way to make postgres not abort the transaction on failed
select?
I have a system that uses ORM to retrieve data; ORM is very slow for some
cases, so there's a perf optimization that issues ANSI SQL queries directly
thru ORM's built-in passthru, and falls back to ORM if they fail.
