Calem Community Forum

Functionality Help => FAQ => Topic started by: kopunski on January 13, 2008, 11:44:56 pm

Title: id numbering in importing process..
Post by: kopunski on January 13, 2008, 11:44:56 pm

currently i'm migrating my excel database to calemeam database with a help from navicat tool. to assign the id numbers of the new data, i use new numbers with sequential order. fo example, if the last id number on calemeam database is:
2c1171fd-ec3e-1414-15b3-eee308327816

then i will use:
2c1171fd-ec3e-1414-15b3-eee308327817
to:
2c1171fd-ec3e-1414-15b3-eee308327827

for let say 10 new entries.

this is what i do. now, i want to know if this okay? i mean if i use calemeam internal module to input new data, surely it will generate new random id number. but will it going to be a conflict with the id numbers that i've already make/input?

Title: id numbering in importing process..
Post by: calemadmin on January 14, 2008, 11:01:44 am

It might be a problem if you go by the format used by CalemEAM. To avoid conflict you could change the format for the numbers you manually generated, for instance:
2c1171fd-ec3e-1414-15b3-eee308327817 => 2c1171fd-ec3e-1414-15b3+eee308327817

change the last '-' separator to '+'.

Title: id numbering in importing process..
Post by: kopunski on January 15, 2008, 02:32:26 am

oic.. thanks for the info. will do that..

Title: Why the huge id numbers?
Post by: redjim on April 18, 2008, 12:43:39 pm

Why are the id's on all the tables, such hugemongous numbers.  Why not just increment 1,2,3 ??
I have never seen this before.  Is this some sort of coding convention that I have just not seen?
Or is this some sort of security feature?
I have to import some data to assets, so I am going to have to add the id number in the manufacturer, catagory, etc.  

It seems like this type of numbering requires more database, hard drive, memory resources?

Thanks, James