When running a query with a bind variable, an error message is returned. The error message can differ depending on what the column data type is that the bind variable is for. It is not detecting the bind variable as a variable. It thinks it is the value being looked for. The same query works fine in versions previous to v3.3. Version 3.3 is the only one giving the error.
An example of a query that is run is…
select * from table
where col_name = '&&_variable'
The replacement symbol (&) had to be changed in TDP 3.3.
TDP now recognizes surrounding '#' signs as the replacement symbol.
WORKAROUND #1:
Instead of starting the bind variable with the & symbol, surround it with # symbols.
Here is an example…
select * from table where col_name = '#variable#'
WORKAROUND #2:
Contact support to get a one-off build that will allow the use of the & symbol for bind variables again.
STATUS:
Feature rolled back in version 3.4. The latest version of Toad Data Point can be downloaded at https://support.quest.com/
