René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Can't use primary keys that aren't auto-increment int","articleBody":"For example, wanting to use UUID v6 as a primary key. What happens when you set up your entities and repositories appropriately for this? Well, it _almost_ works, but then it breaks.\r\n\r\nDue to the way parable-php/orm is written, for inserts, the primary key is always removed from the value set, to allow the sql flavor you're using to auto-generate it. Which, obviously, is a terrible idea when you're using custom primary keys.\r\n\r\nThere's multiple ways of approaching a fix for this, which is either specific about fixing custom primary keys, or offers a more generic way of tying into the insert process (perhaps even update, delete?).\r\n\r\nSpecific: Introduce `HasCustomPrimaryKey` and skip the id auto-removal upon insert if set.\r\nGeneric: Introduce `beforeInsert(array $values)` and possibly more. If implemented, would it just skip the default logic?\r\n\r\nWhat if both?\r\n\r\n```\r\ninterface HasCustomPrimaryKey {\r\n    protected function beforeInsert(array $values): array;\r\n}\r\n```","author":{"url":"https://github.com/devvoh","@type":"Person","name":"devvoh"},"datePublished":"2022-04-16T08:12:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6/orm/issues/6"}