Why not use UUID for PK?

[mrgaolei]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Now PrimaryKey type is int, for 'drives', 'charges' etc..
When I have deploy more instance, for example:
On AWS, I run Teslamte sine 2021-2023,
On my NAS, I run Teslate sine 2023-2024.
int PK can't merge those data.
If change to UUID, it can be merge.

Expected Behavior

No response

Steps To Reproduce

No response

Relevant log output

Database issues

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.24.1

[JakobLichterfeld]

Thanks for reporting.

Can you elaborate on your use case? If you have two instances collecting the same data, why would you want to merge them?

Version

v1.24.1

Even if unrelated, this versions is outdated.

[brianmay]

Use of UUIDs everywhere is not going to be a magic bullet that solves all these issues (and may have some other issues I don't want to go into here). For example, you would still end up with two sets of cars, and not sure I see any benefit here over just having two databases.

It is clear however that we really could use some sort of tool that will take two databases, a list of instructions concerning which cars (and maybe other resources) are the same, and output a new merged database.