| ▲ | AntiUSAbah 2 hours ago | |
You let users generate a UUID? To be honest, the chance that you are doing something weird is probably higher than you experiencing a real UUID conflict. How did your database 'flag' that conflict? | ||
| ▲ | mittermayr 2 hours ago | parent [-] | |
user-generated (as in: on the user's phone) was only at the very early stages of this product, and we've since moved to on-server. It's a cash-register type of app, where the same invoice must not be stored twice. So we used to generate a fresh invoice_id (uuidv4) on the user's device for each new invoice, and a double-send of that would automatically be flagged server-side (same id twice). This has since moved on to a server-only mechanism. The database flagged it simply by having a UNIQUE key on the invoice_id column. First entry was from 2025, second entry from today. | ||