Non-autogenerated PKs in squeryl-record #901

rusho opened this Issue Feb 19, 2011 · 3 comments


None yet
5 participants

rusho commented Feb 19, 2011

In squeryl-record, there should be an option to have non-autogenerated PKs. Currently mixing in KeyedRecord trait makes PK autogenerated and without mixing that trait, one cannot use table in relationships, as for that, KeyedEntity is required.

@ghost ghost assigned migo Mar 1, 2012

@ghost ghost assigned davewhittaker Jun 4, 2012


davewhittaker commented Nov 2, 2012

Jan, is this still an issue for you? I can't remember the circumstances around it, and I believe that autogenerated PKs can be disabled in SquerylRecord by declaring:

on(table)(t => declare( is primaryKey))

In other words, if you declare that the field is a primary key without explicitly saying that it is autogenerated, the default behavior should be disabled.


Shadowfiend commented May 10, 2014

Given no feedback and an indication that it should be resolved, I'm going to go ahead and close this issue. Feel free to reopen if it's still a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment