Copy collection does not create new sequence for primary key

[thomasstorm]

If a collection is copied using the geoDB (client), there is no new sequence created for the primary key within the new collection. That is not necessarily a problem, albeit a bit crooked. But when a user shall be granted access to such a copied collection, geoDB looks for the sequence with the name of the new collection, doesn't find it and throw an error.

Reproduce:

g.copy_collection('danube_delta', database="geodb_geodb_doors-admin", new_collection='danube_delta',  new_database="doors")
g.grant_access_to_collection('BSWQDB_1', 'geodb_doors-user', database="doors")
->  GeoDBError: {"hint":null,"details":null,"code":"P0001","message":"No sequence for collection doors_BSWQDB_1"}

Hints for fix:
https://www.postgresqltutorial.com/postgresql-tutorial/postgresql-serial/
https://dba.stackexchange.com/a/91658