escaping \n inside TEXT field

I have a text field that contains \n. When I access my data via Hasura, it adds extra slash to it resulting: \\n. I tried couple of ways to work around it like adding /\n but that resulted to /\\n. All I need to have my text exactly the way I inserted but I assume as you convert value to json friendly, it escapes. Any idea how I can work around it? (Not sure if it is intended or a bug)

[lexi-lambda]

Ah—the issue you’re having is that Postgres does not support \n escapes in ordinary string literals (because SQL does not). So when you write

INSERT INTO test.mytable (title, description)
  VALUES ('title1', 'Some text bla bla bla \n\n and some other');

you’re actually inserting a string with the character sequence “backslash n backslash n” into your database, not a string with newlines. If you want to include newlines in string literals, you can use “‘escape’ string constants,” which are prefixed with the letter E. For example,

INSERT INTO test.mytable (title, description)
  VALUES ('title1', E'Some text bla bla bla \n\n and some other');

will do what you want.

[yogeshwar607]

Ah—the issue you’re having is that Postgres does not support \n escapes in ordinary string literals (because SQL does not). So when you write

INSERT INTO test.mytable (title, description)
  VALUES ('title1', 'Some text bla bla bla \n\n and some other');

you’re actually inserting a string with the character sequence “backslash n backslash n” into your database, not a string with newlines. If you want to include newlines in string literals, you can use “‘escape’ string constants,” which are prefixed with the letter E. For example,

INSERT INTO test.mytable (title, description)
  VALUES ('title1', E'Some text bla bla bla \n\n and some other');

will do what you want.

How we do it in hasura query ?