{"push_id":2870986423,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"c87b9433e3225602e56497f782a610668eac8bf9","before":"1ae5983bc2b267ed7725338ef932505477aee7b8","commits":[{"sha":"c87b9433e3225602e56497f782a610668eac8bf9","author":{"name":"Timo Walther","email":"50f957e7ebf7b4286b7f73838f5eec431c788506@apache.org"},"message":"[FLINK-10281] [table] Fix string literal escaping throughout Table & SQL API\n\nThis commit fixes the string literal escaping of the Table & SQL API. Proper\nescaping of quotes was not possible in the past for Table API. SQL and SQL Client\nwere not standard compliant.\n\nDue to FLINK-8301 backslashes were considered in SQL literals, however, they\nshould only be used in SQL `U&'\\1234'` literals. For the Table API, the new\nlogic relies on the Java/Scala escaping and uses duplicate quotes for escaping\nthe quotes in expression strings. For SQL, we rely on unicode string literals\nwith or without the UESCAPE clause. The SQL Client was using backslashes for\nescaping new lines. For the SQL Client, we allow unescaped new lines and\nuse ';' for statement finalization; similar to other SQL clients.\n\nThis closes #6671.","distinct":true,"url":"https://api.github.com/repos/apache/flink/commits/c87b9433e3225602e56497f782a610668eac8bf9"}]}
{"actor":{"display_login":"asfgit"}}