As I go through the manual process of trying to migrate queries from dbConnect v1.x to dbConnect 3.1.3, I'm having issues with the Edit Input panel.
I follow the steps.
1. Choose a valid connection - check
2. Browse structure and type SQL .... - check
3. Pick a rising column and set the checkpoint value - check
4. Update SQL to accept the checkpoint value and make sure it works.
This is where I run into a problem.The second I start typing "WHERE TIME_STAMP > ? .... The Rising Column dropdown completely empties out and the query returns:
com.microsoft.sqlserver.jdbc.SQLServerException: The value is not set for the parameter number 1. ( No results found )
This makes me unable to save the query and actually set a Rising Column and a Checkpoint Value
If I execute the same query using EVENT_TIME, things work ... but, both EVENT_TIME and TIME_STAMP are 'bigint' objects, and they both show up in the batch query results, so the question would be, why is TIME_STAMP an invalid field to use as a rising column in dbConnect 3 but works perfectly in dbConnect 1?
The target database is MS SQL Server
↧