3 ms·
Is the column limit still a problem for Diesel? The 16 columns max default is not enough and even the optional 26/52 can be too little for some odd legacy schem
by dvdplm 9y ago
Is the column limit still a problem for Diesel? The 16 columns max default is not enough and even the optional 26/52 can be too little for some odd legacy schemas. I'm curious: is this a limitation that will be overcome as the library matures or is it intrinsic to the codegen architecture?
- killercup 9y agoIt's currently dependent on implementing traits for very large tuples, so you could argue it's a language feature we are waiting for (cf. open RFC #1935 [1]). (There was a PR on Diesel to use HLists but it's no longer pursuit.) [1]: https://github.com/rust-lang/rfcs/pull/1935 https://github.com/rust-lang/rfcs/pull/1935
- neverminder 9y agoWhat was the reason you guys dropped HList approach? I'm curious since I have to deal with tables with north of 200 hundred columns and because of forever annoying Scala's tuple parity limit (22) Slick falls back to HList which is really heavy on a compiler and IDE aside from other drawbacks.
- killercup 9y agoThere are some details in https://github.com/diesel-rs/diesel/pull/747 https://github.com/diesel-rs/diesel/pull/747
- rabidferret 9y agoWe didn't want to commit to our own home-grown hlist type until we had some indicator of whether the language was going to go with variadics based on tuples or hlists.
- rabidferret 9y agoIt'll eventually go away when some form of variadic generics lands in the language
- rabidferret 9y agoIf you open an issue we can up the limit again