Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upError on large table definitions #53
Comments
This comment has been minimized.
|
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 |
sgrif
closed this
in
d2d3181
Dec 14, 2015
This comment has been minimized.
|
This is fixed in the next release. You'll need to add |
This comment has been minimized.
lephyrius
commented
Dec 14, 2015
|
@sgrif That's how it is working with legacy code. :) |
This comment has been minimized.
|
Unfortunately since we're working with tuples here, I can't just use an arbitrary number in the macro. (The short version is 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. |
This comment has been minimized.
|
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 |
This comment has been minimized.
|
You can double it again with the "huge-tables" feature |
This comment has been minimized.
|
Well done, sir. Thank you, Sean. |
lephyrius commentedDec 5, 2015
This code works:
This code doesn't work:
It gives this error:
What is wrong? I'm pretty new on rust.🍶