TropicalPenguin opened a new issue, #333:
URL: https://github.com/apache/age/issues/333

   **Describe the bug**
   The following two statements, incorrectly, return the same result:
   
   a)
   ```pgsql
                                                         <TAB>
   SELECT * FROM ag_catalog.cypher('G:1', $$ RETURN "foo        bar" $$) AS 
(result1 ag_catalog.agtype);
   ```
   b)
   ```pgsql
   SELECT * FROM ag_catalog.cypher('G:1', $$ RETURN "foo\tbar" $$) AS (result1 
ag_catalog.agtype);
   ```
   
   Since more than one input can be mapped to an output, this prevents reliable 
round-tripping of string data between database and client. In this example, 
it's impossible to know the difference between a tab character, and the two 
characters literal backslash, literal t.
   
   **How are you accessing AGE (Command line, driver, etc.)?**
   - Command line
   
   **What data setup do we need to do?**
   ```pgsql
   LOAD 'age';
   ```
   
   **What is the necessary configuration info needed?**
   - N/A
   
   **What is the command that caused the error?**
   It's a little hard to enter tabs in this text input, but I trust you get the 
idea:
   ```pgsql
                                                         <TAB>
   SELECT * FROM ag_catalog.cypher('G:1', $$ RETURN "foo        bar" $$) AS 
(result1 ag_catalog.agtype);
   ```
   ```
     result1   
   ------------
    "foo\tbar"
   (1 row)
   ```
   
   **Expected behavior**
   After storing a string in a node or edge property, I should be able to 
retrieve the original string, regardless of whether some situations require the 
string's characters to be escaped. 
   
   **Environment (please complete the following information):**
   - Version: 1.0.0
   
   **Additional context**
   N/A
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to