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 Request: "Unparsing" #674

Open
abhillman opened this issue Oct 17, 2022 · 2 comments
Open

Feature Request: "Unparsing" #674

abhillman opened this issue Oct 17, 2022 · 2 comments

Comments

@abhillman
Copy link

i.e. for a given dialect, go from an AST -> SQL

@AugustoFKL
Copy link
Contributor

@abhillman I don't think this is feasible in the near future.

I think that's more feasible to be done in another project, as a side-project of someone, than as a part of this crate.

That would require one of the two following approaches:

  • Re-structure the AST and have once for each dialect (e.g., SelectPostgresql, SelectAnsi, etc.); or
  • Have a dialect-specific implementation of to_string() of the AST.

Either way, it's a big change, and the current state of the project is basically stable, so huge changes aren't prone to be accepted.

The problem with the second solution, IMHO, is that this would be an expansion in a feature completely new, which would require a big help and supervision from maintainers, which isn't feasible right now.

@tv42
Copy link

tv42 commented Nov 13, 2024

Duplicate of #18, especially #18 (comment)

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

No branches or pull requests

3 participants