public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Tim Starling <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Upsert error "column reference is ambiguous"
Date: Sun, 27 Apr 2025 23:15:23 -0700
Message-ID: <CAKFQuwZzU9D6vuPbWoQM7tGS8EuSoGGCUuFGJuJrhFzmCsjqUg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On Sunday, April 27, 2025, Tim Starling <[email protected]> wrote:
> thus allowing it to DWIM.
We intentionally choose (or, in any case have established) a SWYM approach
here.
Personally I’d be fine with the reduced helpfulness in trying to prevent
buggy queries in the interest of being more conforming with the broader
world. I am curious as to whether we are in strict adherence to the SQL
Standard on this point though. Makes deviation a bit tougher to justify.
It does seem that project policies would prevent back-patching such a
change.
David J.
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Upsert error "column reference is ambiguous"
In-Reply-To: <CAKFQuwZzU9D6vuPbWoQM7tGS8EuSoGGCUuFGJuJrhFzmCsjqUg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox