Why aren’t job ID s standard UUID?
When we create a job using runpod the returned job ID is not a standard UUID. Instead, it’s some UUID with some suffix. I would like to know the reason for this, and also how to standardize the job IDs.
The reason for me to want this is because in our database we store the job ID but it violates UUID constraint
The reason for me to want this is because in our database we store the job ID but it violates UUID constraint
