|
>>Maybe we should just use the one approach for all three areas that gaurantees uniquenesss i.e. use a GUID/UUID based on the date-time of transaction
I originally did not want to do this (use a guid or uuid) as it thought would be too big. Was hoping to use something a lot smaller (originally 12, now increased to 15)
So we currently use a string generated based on the time-stamp for manual transactions. While this would (to a certain degree) guarantee uniqueness, the probability of a duplicate would increase if the same was used in all Automated transactions (say an organization the size of GK doing data entry at a time in all the branches), so had settled on using the loan/savings transaction Id for the same to better guarantee uniquess.
Will have a rethink on the same soon...
|