You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 insql_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.
The text was updated successfully, but these errors were encountered: