Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-26 Thread via GitHub
Lordworms commented on code in PR #14844: URL: https://github.com/apache/datafusion/pull/14844#discussion_r1972142808 ## datafusion-cli/src/helper.rs: ## @@ -310,14 +266,13 @@ mod tests { )?; assert!(matches!(result, ValidationResult::Valid(None))); -

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-26 Thread via GitHub
alamb commented on code in PR #14844: URL: https://github.com/apache/datafusion/pull/14844#discussion_r1971459393 ## datafusion-cli/src/helper.rs: ## @@ -166,40 +154,8 @@ impl Validator for CliHelper { impl Helper for CliHelper {} -/// Unescape input string from readline. -

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-25 Thread via GitHub
findepi commented on code in PR #14844: URL: https://github.com/apache/datafusion/pull/14844#discussion_r1971099360 ## datafusion-cli/tests/cli_integration.rs: ## @@ -39,6 +39,10 @@ fn init() { ["--command", "select 1; select 2;", "--format", "json", "-q"], "[{\"Int64(

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-25 Thread via GitHub
findepi commented on PR #14844: URL: https://github.com/apache/datafusion/pull/14844#issuecomment-2684193983 > I think you are right that this is the core question: "should `datafusion-cli` be doing any escaping / unescaping itself?" no, the CLI should not do thos > If we want

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-25 Thread via GitHub
Lordworms commented on code in PR #14844: URL: https://github.com/apache/datafusion/pull/14844#discussion_r1970592527 ## datafusion-cli/src/helper.rs: ## @@ -326,15 +326,6 @@ mod tests { )?; assert!(matches!(result, ValidationResult::Valid(None))); -

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-25 Thread via GitHub
alamb commented on PR #14844: URL: https://github.com/apache/datafusion/pull/14844#issuecomment-2683322075 > I think this is correct, because postgresql treats line breaks, such as \t \0, as plain text, but in the original design of DataFusion, \t, \0 should be escaped, so for \1, since it

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-25 Thread via GitHub
Lordworms commented on PR #14844: URL: https://github.com/apache/datafusion/pull/14844#issuecomment-2683310903 > Hi @Lordworms -- thank you for this PR > > I played around with it a bit locally and something still doesn't seem right > > Specifically, postgres will treat `\1` li

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-23 Thread via GitHub
Lordworms commented on PR #14844: URL: https://github.com/apache/datafusion/pull/14844#issuecomment-2677595271 ![image](https://github.com/user-attachments/assets/23c8dd3e-c3f1-427b-b9b4-aa6c85bf4c38) -- This is an automated message from the Apache Git Service. To respond to the messa

Re: [PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-23 Thread via GitHub
Lordworms commented on PR #14844: URL: https://github.com/apache/datafusion/pull/14844#issuecomment-2677559931 I haven't find a good place to add tests, but here is the results ![image](https://github.com/user-attachments/assets/01497acb-dc7c-4f9c-bb0c-beab65b0e041) -- This is an a

[PR] correctly treat backslash in datafusion-cli [datafusion]

2025-02-23 Thread via GitHub
Lordworms opened a new pull request, #14844: URL: https://github.com/apache/datafusion/pull/14844 ## Which issue does this PR close? - Closes #13286 ## Rationale for this change ## What changes are included in this PR? ## Are these changes