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.
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
You can use it but it is not recommended to have date time column as rising column.
And also, one you put where TIME_STAMP > 1, then you will be able to see the rising column list again.