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 upChanged column names in `table!` don't make it to `joinable!` #1609
Comments
Eijebong
added
bug
good first issue
mentoring available
labels
Apr 1, 2018
sgrif
changed the title from
Changed column names in `!table` don't make it to `joinable!`
to
Changed column names in `table!` don't make it to `joinable!`
Apr 1, 2018
This comment has been minimized.
meven
commented
Jun 16, 2018
|
I would like to claim this issue. I understand the issue at stake is that in print_schema.rs:250 the outputed foreign_key column does not pass through the RESERVED_NAMES filter in So I wonder which way to go from there, the simplest way I can come up with is to swap in
the foreign_key with the Or in |
This comment has been minimized.
meven
commented
Jun 27, 2018
|
ping @Eijebong does my take make sense ? |
This comment has been minimized.
meven
commented
Jul 16, 2018
|
ping @Eijebong |
This comment has been minimized.
|
Sure, go for it. If you need help we can either discuss it here or on our gitter channel (sorry missed the other ping) |
toddobryan commentedApr 1, 2018
•
edited by sgrif
Setup
Latest version
Problem Description
Using
print-schemaon a pre-existing database, columns namedtypeare correctly changed totype_with a#[sql_name = "type"]attribute, but the underscore is not added in thejoinable!macro later, leading to errors.Checklist