Error on large table definitions about diesel HOT 7 CLOSED

Busted! I only support tuples of an arbitrarily large size, as it takes longer to compile when I increase it. Right now we go to 16 IIRC, I'll bump it to 26

from diesel.

This is fixed in the next release. You'll need to add features = ["large-tables"] to your Cargo.toml, as this change increases our compile time by a ton, and I don't think common usage requires > 16.

from diesel.

@sgrif That's how it is working with legacy code. :)
THX!
Why can't it be configurable? (might be a stupid question by me. Only knowing C++ templates. )

from diesel.

Unfortunately since we're working with tuples here, I can't just use an arbitrary number in the macro. (The short version is self.19 is a valid expression, but self.(19-1) is not.)

So I have to put some boilerplate in to make this work, which means I end up picking some arbitrary number. 26 was what my editor macro to add more impls worked up to.

from diesel.

I'm totally sure it will be not a default case, but at the moment I got three tables (the whole db contains ~ 50 tables) with more than 26 columns (up to 40 columns). Is there are any chance, to get this compiled? I just tried to migrate an old data-structure from MySQL to Pg and would like to do a test-connection with the diesel-demo (, where the structure gets magically converted to ORM 😀 )

from diesel.

You can double it again with the "huge-tables" feature

from diesel.

Well done, sir. Thank you, Sean.

from diesel.