Errors in Invalid SQL should be warnings

[btruong66]

Introduced in v1.3.1, an error is raised when parameters are provided without being used in the prepared SQL:

vertica-python/vertica_python/vertica/cursor.py

Line 657 in fe96db7

raise ValueError(f'Invalid SQL: {operation}'

This exception should be a warning rather than raise an error to maintain backwards compatibility.

[williammatherjones]

I propose we add connection property like strict_prepared_statements. It would be True by default. Setting it to false would cause information to be printed to the log instead of raising an error.

[sitingren]

@btruong66 I'd like to maintain this backwards compatibility by adding an undocumented property (to suppress the exception to a warning), either an environment variable or a connection option, which one do you prefer?

[sitingren]

The workaround is published in vertica-python v1.3.2. You can set environment variable VERTICA_PYTHON_IGNORE_NAMED_PARAMETER_CHECK to 1 to get rid of the exception.

BTW, the code path is not for "prepared SQL", it is for client-side binding (i.e. simple query).

[sitingren]

Closing due to inactivity, reopen if you have more questions.