Rethinking parameterized SQL queries
John Cowan
(27 Feb 2021 01:18 UTC)
|
Re: Rethinking parameterized SQL queries
Lassi Kortela
(27 Feb 2021 09:13 UTC)
|
Re: Rethinking parameterized SQL queries
Lassi Kortela
(27 Feb 2021 09:17 UTC)
|
Re: Rethinking parameterized SQL queries
Lassi Kortela
(27 Feb 2021 09:30 UTC)
|
Re: Rethinking parameterized SQL queries
John Cowan
(27 Feb 2021 20:08 UTC)
|
Re: Rethinking parameterized SQL queries
Lassi Kortela
(27 Feb 2021 20:36 UTC)
|
Re: Rethinking parameterized SQL queries
John Cowan
(27 Feb 2021 22:14 UTC)
|
Re: Rethinking parameterized SQL queries
Peter Bex
(28 Feb 2021 10:21 UTC)
|
Re: Rethinking parameterized SQL queries
John Cowan
(01 Mar 2021 03:29 UTC)
|
Re: Rethinking parameterized SQL queries
Florian Weimer
(27 Feb 2021 12:32 UTC)
|
Re: Rethinking parameterized SQL queries Lassi Kortela (27 Feb 2021 12:39 UTC)
|
Re: Rethinking parameterized SQL queries Lassi Kortela 27 Feb 2021 12:39 UTC
> This is not entirely correct. PostgreSQL uses ? in operator names. > There is even a predefined ? operator for JSON types: > > fw=> SELECT '{"a":true}'::jsonb ? 'a'; > ?column? > ---------- > t > (1 row) More proof that every text-based programming language is on a mission to colonize the entire ASCII range. And Unicode operators are slowly making inroads.