regarding <https://github.com/datalineio/dataline/...
# contributing-to-airbyte
m
u
we should check what behavior a postgres tap has
u
if singer doesn't talk about an encoding scheme for '\n' then we need something like that.
u
@Jared Rhizor (Airbyte)
u
do any taps fail to encode newlines to \n that we know of?
u
we need to check if the one we implemented are doing something special
u
They can not have a requirement like that without explaining what you should do if there is a \n in the data you;re writing
u
is anyone looking a this?
u
sorry didn't see this
u
I changed the sql init file for the acceptance tests to have a record with a newline:
u
Copy code
(
        3,
        'jared
        newline'
    ),
u
tests passed and it replicated the same record that was inserted into the destination postgres
u
Copy code
|  id|name                 |
+----+---------------------+
|   3|jared{lf}        n...|
+----+---------------------+
u
more legibly:
u
I added
System.out.println("sourceTableRecord = " + sourceTableRecord.get("name"));
u
and it outputs:
u
Copy code
sourceTableRecord = sherif
sourceTableRecord = charles
sourceTableRecord = jared
        newline
sourceTableRecord = michel
sourceTableRecord = john
u
so it looks like postgres at least is handling escaping correctly for new lines
u
ok
u
so should just disregard that issue?
u
I think so. If someone breaks this behavior in a tap., it should represent an exceptional breaking case of that tap
u
ok