|
|
It would be helpful to use UUIDs as primary/secondary key fields for row objects for data exchange with other GIS databases. It could also be a better way of generating new IDs than the default approach of sequential numbers, which cause problems when trying to merge models together.
Currently, the primary field(s) and "asset_id" field on most row objects have a 30 character limit. Spatial data (i.e. customer points) have a 25 character limit for their primary key, but a 50 character limit for their secondary key ("identifier"). Both would need to be extended to 36 characters to support UUIDs.
