From: | David Gauthier <davegauthierpg(at)gmail(dot)com> |
---|---|
To: | Tim Clarke <tim(dot)clarke(at)minerva(dot)info> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: What's the best way to translate MS generated translations of user input to what the user actually typed prior to insert or update into PG backend table ? |
Date: | 2020-10-30 17:51:49 |
Message-ID: | CAMBRECBcEka59GMLAY6LmOuuEgYHNRyd2Pkr4gQwVA0Ww8-MAw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <tim(dot)clarke(at)minerva(dot)info> wrote:
>
> 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) decides
> to translate that to what emacs is describing as...
>
> character: … (displayed as …) (codepoint 8230, #o20046, #x2026)
> preferred charset: unicode (Unicode (ISO10646))
> code point in charset: 0x2026
>
> It makes this translation for some users but not others, so I'm assuming
> it has something to do with how individuals set up their Windows env. No
> matter, assume we can't have them change their environment in whatever soln
> we come up with.
>
> I want to change the 0x2026 to the 3 periods which the user entered.
>
> 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 way MS translates double quotes the next day, etc... .
> Is there an elegant way to do this ?
>
> Thanks In Advance for any help !
>
>
> IMHO this is the spelling functionality from Office/Access "correcting"
> your typing, you can probably see it happening as you type and tapping the
> escape key immediately afterwards undoes the "suggestion". You're right in
> that it would need either a desktop change per user or a translation table.
> You can find all the changes though and do them all at once which saves
> your "next day, next day...." issue?
>
> Tim Clarke
>
>
>
> Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 |
> Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1
> 647 503 2848
> Web: https://www.manifest.co.uk/
>
>
>
> Minerva Analytics Ltd - A Solactive Company
> 9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United
> Kingdom
>
> ------------------------------
>
> Copyright: This e-mail may contain confidential or legally privileged
> information. If you are not the named addressee you must not use or
> disclose such information, instead please report it to admin(at)minerva(dot)info
> Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd:
> Registered in England Number 11260966 & The Manifest Voting Agency Ltd:
> Registered in England Number 2920820 Registered Office at above address.
> Please Click Here https://www.manifest.co.uk/legal/ for further
> information.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2020-10-30 18:13:05 | Re: What's the best way to translate MS generated translations of user input to what the user actually typed prior to insert or update into PG backend table ? |
Previous Message | Rich Shepard | 2020-10-30 16:46:57 | Re: Drop column constraint [FIXED] |