That clears things up for me. I hadn’t considered the distinction between the puzzle’s business key and an auto-incrementing surrogate key, or the fact that auto-increment values aren’t guaranteed to be consecutive.
I’ll keep the puzzle_date/puzzle_type combination as the business-level uniqueness constraint and use the auto-increment ID where I need a simple FK target.
Thanks for the explanation — I have a much clearer idea of how I want to structure this now.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | File and post data confusion in PHP | 0 | 5.97 | 10-06-2026 |
| 2 | Using a static flag to prevent setting twice | 0 | 14.14 | 24-09-2026 |
| 3 | Making Django unique constraints case-insensitive (with no downtime) | 0 | 14.22 | 08-03-2026 |
| 4 | Building a smart condominium & property management platform | 0 | 17.6 | 24-09-2026 |
| 5 | risetechapps/api-key-for-laravel | 0 | 100 | 03-08-2026 |
| 6 | Webuzo 4.7.5 Launched | 0 | 9.23 | 11-08-2026 |
| 7 | Re: Issue with Spline IK Solver misalignment on a bone chain | 0 | 5 | 18-07-2026 |
| 8 | Re: Understanding Distributed Locking in Production Schedulers | 0 | 8.86 | 23-09-2026 |
| 9 | Comment on Contribute to the Plugins Team! by akash19jan | 0 | 13.78 | 21-03-2026 |