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 upinferring PK from existing schema #704
Comments
This comment has been minimized.
|
I am able to reproduce the issue. |
This comment has been minimized.
|
I've identified the issue and am working on a solution. The issue only occurs when no schema name is specified on the table. As a workaround, you can write |
This comment has been minimized.
|
I still need to look into the issue you were seeing on 0.10.1, as that should have been fixed. The issue with the primary key lookup was only an issue on master, not the released version (and we would have shipped with that bug in place had you not stumbled onto it) |
added a commit
that referenced
this issue
Feb 14, 2017
sgrif
referenced this issue
Feb 14, 2017
Merged
Fix `infer_table_from_schema!` when no schema name is given #705
This comment has been minimized.
dvdplm
commented
Feb 15, 2017
|
Wow, that was fast! :) |
sgrif
closed this
in
#705
Feb 15, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dvdplm commentedFeb 14, 2017
Using the table definition below and the
infer_table_from_schema!macro I'm getting an odd error:error: proc-macro derive panicked.The above SQL is an extract from the dump that
pg_dumpproduces so it's perhaps not the way a human would have written it but results in a perfectly valid table. This SQL adds rows and increments the PK:Rust version:
Cargo.toml:
The code that runs is essentially the "getting_started_step_1" without any migrations generated as I'm trying to see how Diesel and Rust performs on my existing schema.
Full error output: