Using dbconnect rising input for Oracle table

[GabrieleD]

Hello,

we would like to use the rising input mode for a dbconnect (2.x) query.

Unfortunately, the destination table is an Oracle table and it only has a date field that could be used as rising column, but, if I'm right with the documentation, this may lead to duplicates.

Is this correct? Is there any other way to solve this problem without modifying the source table?

Thanks

[isoutamo]

Hi

if the field's type is date then it (almost sure) contains duplicates. If it's date time with enough ms or even smaller partitions then it may be usable. But as it said the best option is use separate sequential (or what it was called in Oracle world?) which has auto increment or something similar feature in use.

You need to remember that you are sorting in all query those lines/resultset by this field and continue from it's previous values + 1. Otherwise you will miss some values or you will get duplicates.

r. Ismo