On Tue, 9 Mar 2021 13:33:19 -0700 "David G. Johnston" <david.g.johnston@xxxxxxxxx> wrote: > > By using "G" you are giving up control and letting your locale settings > decide what gets output. You can continue to use to_char but take control > back by being explicit, or pass actual numbers into and out of the database > and let your front-end deal with presentation concerns. I suggest the > latter. Well, that was a fast answer :-) Indeed, replacing "G" with \s works. However, the application is destined to be multi-lingual, and number formats vary widely between countries : 1,000.25 (US) 1'000,25 (CH) 1 000,25 (FR) 1.000,25 (GER) etc... So, I intended to follow this advice by Tom Lane : https://www.postgresql-archive.org/GENERAL-setting-LC-NUMERIC-td1857521.html Having a database with the proper lc_numeric setting for each country, and using to_char/to_number to manipulate numbers is much more appealing than writing my own parser in my front end. But this weird space is getting in my way. -- Bien à vous, Vincent Veyron https://marica.fr/ Logiciel de gestion des sinistres assurances, des dossiers contentieux et des contrats pour le service juridique
