Hi,
I just noticed that my 64-bit hashcode generated ids get truncated (actually rounded) and that this seems to be a JS limitation.
So they're better dealt with as Strings in SGWT/JS.
I wonder what you consider best practice in this case if the DB uses full range (bigint(20)) numbers as ids.
Is there something like built-in autoconversion from String to int and vice versa or do I need to solve the conversion on a lower level?
Just changing the type of the id field to text did not seem to make a difference and converting the id to a string in a DMI does not seem to help either.
(The ids seem to be truncated on the server as the console already shows them truncated whereas in a bean, they are OK.)
Thanks,
fatzopilot
SmartClient Version: v8.3p_2013-09-07/PowerEdition Deployment (built 2013-09-07)
I just noticed that my 64-bit hashcode generated ids get truncated (actually rounded) and that this seems to be a JS limitation.
So they're better dealt with as Strings in SGWT/JS.
I wonder what you consider best practice in this case if the DB uses full range (bigint(20)) numbers as ids.
Is there something like built-in autoconversion from String to int and vice versa or do I need to solve the conversion on a lower level?
Just changing the type of the id field to text did not seem to make a difference and converting the id to a string in a DMI does not seem to help either.
(The ids seem to be truncated on the server as the console already shows them truncated whereas in a bean, they are OK.)
Thanks,
fatzopilot
SmartClient Version: v8.3p_2013-09-07/PowerEdition Deployment (built 2013-09-07)