github-actions[bot] commented on issue #15048:
URL: 
https://github.com/apache/dolphinscheduler/issues/15048#issuecomment-1770152021

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I create sql task in 3.2.0 version. write two sql command in one sql task. 
use ;\n to separate it. but it execute fail.
   i view database in ds. it save ;\r\n, not ;\n. cause not correctly separate 
it.
   
   I installed a 3.2.0 version of dolphinscheduler, created a Sql task, and 
wrote two SQLs in the task, and then the execution failed.
   
   ### What you expected to happen
   
   because ;\n is default sql separator, write more sql command in one sql 
task, it should separate it correctly.
   
   Because the default separator for sql tasks in version 3.2.0 dophinscheduler 
is;\n, normally it should be able to execute normally.
   
   ### How to reproduce
   
   1. create a sql task.
   2. write two sql command in created sql task. for example
   ```
   select current_date();
   select current_date()
   ```
   3. execute online
   4. start execute
   
   
   1. Create a Sql task
   2. Add two sql commands to the created Sql task, for example
   ```
   select current_date();
   select current_date();
   ```
   3. Online workflow
   4. Execute workflow
   
   ### Anything else
   
   Tracking the code, it was found that the sql delimiter stored in the 
database was;\r\n, which caused the code to be unable to split multiple SQLs 
normally, and ultimately the sql task failed to execute.
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
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