David Gauthier writes:
> Next question, how does one actually replace the thing ?
> replace(thestring,0x2026,'...')
> ... isn't going to fly.
If you don't want to write the actual UTF8 character, maybe the chr()
function would suit you better [1].
regards, tom lane
[1] h
On 2020-10-30 13:51:49 -0400, David Gauthier wrote:
> Next question, how does one actually replace the thing ?
> replace(thestring,0x2026,'...')
> ... isn't going to fly.
> Working with binary values in PG isn't at the top of my resume :-)
Either just type (or copy/paste) it:
select replace
Next question, how does one actually replace the thing ?
replace(thestring,0x2026,'...')
... isn't going to fly.
Working with binary values in PG isn't at the top of my resume :-)
On Fri, Oct 30, 2020 at 12:20 PM Tim Clarke wrote:
>
> On 30/10/2020 16:03, David Gauthier wrote:
>
> psql (11.5, s
On 30/10/2020 16:03, David Gauthier wrote:
psql (11.5, server 11.3) on linux
I'm using MS-Access as a Windows front-end to a PG DB table through ODBC
(PostgreSQL Unicode ODBC Driver). Seems to be working fine except for when
users enter "..." as part of a string, MS (in it's infinite wisdom) d
On Fri, Oct 30, 2020 at 9:03 AM David Gauthier
wrote:
> I was thinking of a pre-insert and pre-update trigger which could make the
> translation. But I'd rather not try to do this one char at a time...
> translate "..." today to fix today's issue, then "--" tomorrow when that
> pops up, then the
psql (11.5, server 11.3) on linux
I'm using MS-Access as a Windows front-end to a PG DB table through ODBC
(PostgreSQL Unicode ODBC Driver). Seems to be working fine except for when
users enter "..." as part of a string, MS (in it's infinite wisdom) decides
to translate that to what emacs is desc
