internally using real column name and alias is for external api only
This commit is contained in:
@@ -6,6 +6,9 @@ pub struct RelationshipHop {
|
||||
pub from_table: String,
|
||||
pub to_table: String,
|
||||
pub fk_source_table: String,
|
||||
/// The link column's real name, the one the database answers to. Aliases
|
||||
/// change; a path stored in aliases would have to be rewritten every time
|
||||
/// one did, and it is read straight into SQL.
|
||||
pub fk_column: String,
|
||||
}
|
||||
|
||||
@@ -13,9 +16,8 @@ pub struct RelationshipHop {
|
||||
pub struct RelationshipLink {
|
||||
pub source_table: String,
|
||||
pub target_table: String,
|
||||
/// The column carrying the link, which is the name it was given. A table
|
||||
/// may link to one target several times, so the target's name does not
|
||||
/// identify the column.
|
||||
/// The link column's real name. A table may link to one target several
|
||||
/// times, so the target's name does not identify the column.
|
||||
pub fk_column: String,
|
||||
}
|
||||
|
||||
|
||||
2
server
2
server
Submodule server updated: c5ff2c81f1...598521ccd4
Reference in New Issue
Block a user