Subject: | Re: Postgresql Character escaping
| Date: | Wed, 6 May 2020 11:28:54 +1000
| From: | Tom Krieg <REMOVEtomkCAPITALS@sdassociates.com.au>
| Newsgroups: | pnews.paradox-client_server
|
That's the way I did it with Paradox. I found that the BDE got in the
way with anything else, even for passs through sql.
On 6/05/2020 7:10 am, Mark Bannister wrote:
> Trying to find the best method of escaping text properly for inserting
> into a table. I thought I could use dollar quoting $$mystring$$ but the
> bde is for some reason trying to parse remote queries and chokes if
> there are single or double quotes in the text.
> so this fails because of the single quote '
> INSERT INTO __test_table
> (text_test)
> VALUES($$fr"ed2$$ );
>
> The only thing that I found that appears to be working is using the
> escape "e" pg style and doubling all ' " \ when they appear
> INSERT INTO __test_table
> (text_test)
> VALUES(E'fr""ed2' );
> works with value = 'fr"ed'
>
> --
> Mark B
>
|