5 ms·
I think the only place I've seen anyone wanting more than 22 parameters was people who had a database table with more than 22 rows (!) and where using the SLICK
by thescrewdriver 13y ago
I think the only place I've seen anyone wanting more than 22 parameters was people who had a database table with more than 22 rows (!) and where using the SLICK library.
- royjacobs 13y agoSo basically, anyone with a legacy database :)
- dk8996 13y agoYeah we ran into this problem... Scala and the whole ecosystem can get annoying. In the real world, outside of the academic bubble that Scala lives in, database tables are over 22 columns.
- bad_user 13y agoIn Scala I find it more natural to group multiple columns together / break the case-class representing the table into multiple case-classes. The problem is that Slick needs to serialize/deserialize those case-classes into tuples.
- frowaway001 13y agoI think the arity limit is more or less planned to be fixed in Scala > 2.11 anyway.
- thescrewdriver 13y agoSeems to be fixed in v2.0: http://slick.typesafe.com/news/2014/01/21/slick-2.0.0-released.html http://slick.typesafe.com/news/2014/01/21/slick-2.0.0-releas...
- VLM 13y agoYou can also run into it with forms in play, although for a variety of reasons you hit it at 18. The whole situation just drips with arrogance... "we have a magic number, and if you hit it, you suck"
- dk8996 13y agoI agree. I know people posted a comment saying its fixed in 2.11 but if Scala wants to be production ready language it shouldn't take 10 years to address this.
- frowaway001 13y ago> "we have a magic number, and if you hit it, you suck" You mean like Java does since ... forever?