Hello!
Do you have experince using MySQL BIGINT type of field? Looks like Servoy doesen’t work properly with data of that kind of field.
I have a bunch of tables that use BIGINT, and I would not like to convert them to use INTEGER.
Nikola
Hello!
Do you have experince using MySQL BIGINT type of field? Looks like Servoy doesen’t work properly with data of that kind of field.
I have a bunch of tables that use BIGINT, and I would not like to convert them to use INTEGER.
Nikola
What problems do you have? I can use bigint’s without any problems
Problem is that I can not use 17-digit number as a primary key. I touch the limit somewhere around 2 147 000 000, and bigger numbers Servoy change in negative numbers.
That is the reason why I was not able to join my tables (I have post qustion about it few weeks ago).
The reason we use such a large number is since records are being created remotely by client machine and thus we have to be able to insure that each new Primary Key is unique by having the first digit be the interface used to enter the new record (1 for FileMaker, 2 for Web and 3 for Servoy). The next three digits represent the user id, the next six digits represent the date and the last six represent the time.
Can you give me some advice please?
Could you trim the date to 4 characters since we’re so early in the century …
Either that or have seperate auto entered fields that input the creation dates and times upon record creation. If you felt the need to see what the record ID would have been you could concantonate the ID, the date & time created fields.
We have pretty much decided to try to never use meaningful keys in our FMP → Servoy rewrite because of these types of questions as well as other issues.
How about using a text field. I use a text anyway if any concatenation is being done.
Jan,
The indexing of varchar’s is not as efficient as that of BigInt. One of our programmers, Mladen, work extensively with Oracle Hash KEYS that were BIGINT. Is this a Java restriction or a Servoy restriction? As Mladen said during a recent conversation regarding this issue, the inability to use bigint’s as primary and foreign keys would limit the ability for Servoy to work with large hash values used in Oracle.
I can have Mladen e-mail you directly or sign up to post if he can better share his thoughts on this.
All the best,
Dino