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

Query parameter support for engine identifier #61865

Open
jkaflik opened this issue Mar 25, 2024 · 2 comments
Open

Query parameter support for engine identifier #61865

jkaflik opened this issue Mar 25, 2024 · 2 comments

Comments

@jkaflik
Copy link
Contributor

jkaflik commented Mar 25, 2024

Describe the unexpected behaviour

Currently, it's not possible to pass an table engine name as a query parameter:

  CREATE TABLE IF NOT EXISTS {table:Identifier} (
  		key String
  	, value String
  	, expiration DateTime
  ) ENGINE={engine:Identifier}

It's not correctly handled in the parser and results in Unknown table engine . (UNKNOWN_STORAGE) error. (empty engine name)

How to reproduce

Expected behavior

ENGINE={engine:Identifier} is substituted before the table engine parse.

@alexey-milovidov
Copy link
Member

I think it is not worth it.

@alexey-milovidov alexey-milovidov added the st-wontfix Known issue, no plans to fix it currenlty label Mar 25, 2024
@mirusky
Copy link

mirusky commented Apr 9, 2024

More than 1 developer requesting it, maybe you need to reconsider.

Since the current solution is to use "string replacement", it is opening the door for SQL Injection.

I think using engine identifier could save us since it can be sanitized

@alexey-milovidov alexey-milovidov added help wanted and removed st-wontfix Known issue, no plans to fix it currenlty labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants