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

Exotic column name from mysql #103

Open
Iced-Sun opened this issue Aug 13, 2019 · 1 comment
Open

Exotic column name from mysql #103

Iced-Sun opened this issue Aug 13, 2019 · 1 comment
Assignees

Comments

@Iced-Sun
Copy link

Iced-Sun commented Aug 13, 2019

I ran into a situation that a column name like smart_name_to_break_your_tool_copy(3) (be aware of the parenthesis) would stop pg_chamelon from working. It is obvious the regex magic in sql_util.py cannot handle sufficiently arbitrary sql statements.

I worked it around by adding some ad-hoc and ugly hacks to the regex, but I doubt it to be a correct solution to the problem.

Would it be possible to make the sql parser more robust?

Thank you very much for the work! pg_chameleon really helps me a lot.

Regards.

@the4thdoctor
Copy link
Owner

Hi, I'm picking the project again after a long hiatus and I'll do a new bugfix release soon. I'll try to add the sql parser fix to this release. thanks

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

2 participants