Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature][SQL] Can support #{} similar to mybatis #15171

Closed
3 tasks done
fuchanghai opened this issue Nov 16, 2023 · 4 comments
Closed
3 tasks done

[Feature][SQL] Can support #{} similar to mybatis #15171

fuchanghai opened this issue Nov 16, 2023 · 4 comments
Labels
discussion discussion feature new feature

Comments

@fuchanghai
Copy link
Member

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

image
image

Use case

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@fuchanghai fuchanghai added feature new feature Waiting for reply Waiting for reply labels Nov 16, 2023
@ruanwenjun
Copy link
Member

ruanwenjun commented Nov 18, 2023

Is there any advantage to use # rather than $? I don't think we need to deal with SQL injectionin sql task

@ruanwenjun ruanwenjun added discussion discussion and removed Waiting for reply Waiting for reply labels Nov 18, 2023
@fuchanghai
Copy link
Member Author

hi @ruanwenjun We now have a use case where the sql type node in the current process definition needs an output type variable declared by the subprocess definition that depends on the subprocess type node. This subprocess definition is referenced by many parent canvases. The advantage is that when we need to change, we only need to change the variable values in the subprocess definition, instead of changing all the canvases

@fuchanghai
Copy link
Member Author

hi @ruanwenjun We now have a use case where the sql type node in the current process definition needs an output type variable declared by the subprocess definition that depends on the subprocess type node. This subprocess definition is referenced by many parent canvases. The advantage is that when we need to change, we only need to change the variable values in the subprocess definition, instead of changing all the canvases

We need to concatenate this sql statement using variables of the output type of the upstream node

@fuchanghai
Copy link
Member Author

This function has been implemented,i will close this issue ,and add some documents
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion discussion feature new feature
Projects
None yet
Development

No branches or pull requests

2 participants