I've realised recently that migrating the primary keys to UUIDs will potentially have a large benefit in then being able to implement #383 (django-postgres-copy implementation).
Currently the default integer values are used which is fine, but has the complication that it becomes difficult to set primary keys manually. To implement the Postgres copy method - which should significantly speed up the database writing - the primary keys (or at least an index key) should be declared on upload and used for foreign keys. Generating UUIDs would be good for this and is a common practise.
At the moment the index values are returned on the upload step and are used from that point on.
Would have to be a careful migration but might be worth it.
I've realised recently that migrating the primary keys to UUIDs will potentially have a large benefit in then being able to implement #383 (
django-postgres-copyimplementation).Currently the default integer values are used which is fine, but has the complication that it becomes difficult to set primary keys manually. To implement the Postgres copy method - which should significantly speed up the database writing - the primary keys (or at least an index key) should be declared on upload and used for foreign keys. Generating UUIDs would be good for this and is a common practise.
At the moment the index values are returned on the upload step and are used from that point on.
Would have to be a careful migration but might be worth it.