Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
This issue seems to come up every second week. This becomes more pressing as people play with various kinds of code generation or adopt Slick (and have more than 22 database columns).
There doesn't seem to be an agreement yet on how to handle this, but now there is at least a ticket.
Selection of older discussions:
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-7099?orig=1
Affected Versions: 2.9.2, 2.10.0, 2.11.0-M1
Sorry, something went wrong.
Vladimir Nicolici (vladnc-at-gmail.com) said:
Another ORM affected by the 22 limit is scala-activerecord: aselab/scala-activerecord#27
Also mentioned in that issue is the play framework JSON inception.
Lev Brailovskiy (lev4ik) said:
When this issue is planed to be solved?
Leonard Schneider (leonard.schneider) said:
Case classes has been fixed in #7098 from Scala 2.11.0.
No branches or pull requests