> On 1 Jul 2019, at 12:19, Maarten van Gijssel wrote:
>
> After I posted the question, I realised my mistake 😅. I was using the pg gem
> in Ruby to run the SQL "SELECT encode('123\000\001', 'base64')", the double
> quotes ensure the `\0` will be interpreted as a null byte hence throwing the
>
After I posted the question, I realised my mistake 😅. I was using the pg
gem in Ruby to run the SQL "SELECT encode('123\000\001', 'base64')", the
double quotes ensure the `\0` will be interpreted as a null byte hence
throwing the error. Sorry, my mistake!
Regards,
Maarten
Op ma 1 jul. 2019 om 11:
> On 29 Jun 2019, at 12:45, PG Doc comments form wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/functions-string.html
> Description:
>
> Either I'm doing something wrong or the example `encode('123\000\001',
> 'base64'
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/functions-string.html
Description:
Either I'm doing something wrong or the example `encode('123\000\001',
'base64')` will always result in a parsing error "string contains null
byte".
