On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote:
> If locale_provider is builtin, then locale or builtin_locale must be
> specified and set to either C or C.UTF-8.
>
> It clearly says "locale or builtin_locale", emphasis on the OR.
>
> So two issues here.
> 1) the doc is wrong or misl
On Thu, 2025-06-05 at 15:07 +0200, Dominique Devienne wrote:
> But isn't the point of the new-in-v17 builtin provider is to be
> system
> independent???
Yes, a major part of the builtin provider is complete consistency
across platforms for the entire collation system -- anything affected
by the da
Dominique Devienne wrote:
> So you're saying datcollate and datctype from pg_database are
> irrelevant to PostgreSQL itself, and only extensions might be affects?
Almost. An exception that still exists in v18, as far as I can see [1],
is the default full text search parser still using lib
On Thu, 2025-06-05 at 11:34 +0200, Dominique Devienne wrote:
> On Thu, Jun 5, 2025 at 11:07 AM Dominique Devienne
> wrote:
> > So... It is possible to have the SAME command on Windows and Linux,
> > which yields the SAME datcollate and datctype values???
> > So far, such a command eludes me, I'm a
> In my case, m_new_data is actually a table row type rather than plain
> "record". The row is passed on to another function which calculates the
> altered columns and logs the changes.
In my experience, to specify composite-typed receiver as one element
of INTO list, it need to be column of compo
On Thu, Jun 5, 2025 at 5:01 PM Daniel Verite wrote:
> Dominique Devienne wrote:
> > > locale 'C.UTF-8' or lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8'
> > > cannot work on Windows because Windows does not have a locale
> > > named C.UTF-8, whereas a Linux system does (well at least recent
> >
Dominique Devienne wrote:
> > locale 'C.UTF-8' or lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8'
> > cannot work on Windows because Windows does not have a locale
> > named C.UTF-8, whereas a Linux system does (well at least recent
> > Linuxes. Some old Linuxes don't).
>
> But isn't the point o
On Thu, Jun 5, 2025 at 2:40 PM Daniel Verite wrote:
> Dominique Devienne wrote:
> > On Linux, no error unlike on Windows (still inconsistent there IMHO),
> > but the result is slightly different for datcollate and datctype (C vs
> > en_US),
> > while the same for datlocprovider and datloca
Dominique Devienne wrote:
> On Linux, no error unlike on Windows (still inconsistent there IMHO),
> but the result is slightly different for datcollate and datctype (C vs
> en_US),
> while the same for datlocprovider and datlocale, what I looked at.
>
> Thus I kinda persist that there *is
Am Wed, Jun 04, 2025 at 10:41:15PM + schrieb Glen K:
> In my experience developing backends for APIs, I have
> never come across a case where comments were needed or
> desired within SQL statements generated for API requests,
Being able to garnish with comments the SQL being sent to a
backend
On Thu, Jun 5, 2025 at 1:40 PM Laurenz Albe wrote:
> On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote:
> > It clearly says "locale or builtin_locale", emphasis on the OR.
>
> You are right, and that's how it works on Linux.
> BUILTIN_LOCALE is not required.
Still, required or not, they
On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote:
> Thanks Laurenz. Indeed, Using LOCALE vs BUILTIN_LOCALE matters.
>
> On Linux, no error unlike on Windows (still inconsistent there IMHO),
> but the result is slightly different for datcollate and datctype (C vs en_US),
> while the same
On Thu, Jun 5, 2025 at 11:07 AM Dominique Devienne wrote:
> So... It is possible to have the SAME command on Windows and Linux,
> which yields the SAME datcollate and datctype values???
> So far, such a command eludes me, I'm afraid. --DD
So I tried to be explicit about lc_collate and lc_ctype to
On Thu, Jun 5, 2025 at 4:52 AM Jeff Davis wrote:
> > On Windows, I'm getting
> I tried on windows and linux and got the same result.
Thanks Jeff, for your informative email. The command work,
just like it does on Linux. YET... The results are NOT the same!
C:\Users\ddevienne>psql service=my17
ps
On Thu, 5 Jun 2025 at 01:06, Tom Lane wrote:
> ... An injection attack is normally
> trying to break out of a quoted string, not a comment.
I think the comments he refers to are more used to do "bobby tables"
like stuff, as helpers in correct statement forming, not to inject per
se.
( I do not t
On Thu, Jun 5, 2025 at 3:01 AM Laurenz Albe wrote:
> On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote:
> > The command I'm using (from a libpq trace) is:
> >
> > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8'
> > locale_provider 'builtin' template template0
> >
> > On Window
16 matches
Mail list logo
