On Wed, 2024-05-15 at 14:39 -0400, Tom Lane wrote: > The thing that was bothering me most about this is that I don't > understand why that's a useful check. If I meant to type > > UPDATE mytab SET mycol = 42; > > and instead I type > > UPDATEE mytab SET mycol = 42; > > your proposed feature would catch that; great. But if I type > > UPDATE mytabb SET mycol = 42; > > it won't. How does that make sense?
It makes sense to me. I see a clear distinction between "this is a valid SQL statement" and "this is an SQL statement that will run on a specific database with certain objects in it". To me, "correct syntax" is the former. Yours, Laurenz Albe
