We use unsigned bigint in sybase ASA as pk datatype.
All Database ValueLists using pk as reference for values have the same strange behaviour:
- The associated value is displayed correctly when browsing records.
- The associated value is NOT displayed correctly when changing it or putting it for the first time.
This looks very weird, especially in lists where you can have a column with mixed display of IDs and associated values:
*********************************
* OrderID * Customer *
*********************************
* 23560 * Samsung electronic *
* 23561 * Samsung electronic *
* 23562 * 4711 *
* 23563 * Samsung electronic *
* 23564 * Samsung electronic *
* 23562 * 4711 *
* 23562 * 4711 *
* 23567 * Samsung electronic *
* 23568 * Samsung electronic *
* 23569 * Samsung electronic *
* ... * *
*********************************
As a matter of fact here ‘4711’ is the real value in dataprovider but is not replaced in all lines when using unsigned bigint as datatype.
The bug appears only when creating a new record, or changing a value. If you restart application, all columns will be displayed well again.
If we create a database using integer instead, everything goes well, but integer is far too small for our use.
Will you please check this or suggest us a workaround?