By far the easiest is to use id and not worry about it.
If it's that important, I would suggest leaving id as-is and either adding a
new field or using a virtual field that does a simple hash. I've seen hashes
as simple as multiplying by a small prime number like 1007.
So:
Field('bigid', 'integ
Well, length of an integer field is always the same...
but I understand what you want to mean, because I am on the same
situation
I guess you are looking for an ID to identify records, but It's not
convenient that the ID indicates the order of creation
In my case, is the affiliate ID, and I've b
2 matches
Mail list logo