should use mapped column and table names
See original GitHub issuesince this is supposed to be the actual database diagram, shouldn’t the generated dbml use the mapped table and column names from @map
and @@map
?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Map Table and Column Names in Data Source - Wyn Enterprise
Mapping the table and column names between the data source and the dataset ... Users should use the original table name and column...
Read more >Mapping tables and columns - SQL Compare 15
If you want to compare columns in a table and the column names are different, you can map the columns as required. SQL...
Read more >Mapping Table Columns - SQLAlchemy 1.4 Documentation
A mapping by default shares the same name for a Column as that of the mapped attribute - specifically it matches the Column.key...
Read more >Map tables and columns - Documentation - Devart
Mapping columns option is useful when you need to compare columns in a table and the column names are different. In this case,...
Read more >Column Mappings - Data Abstract Documentation
Lets see how Column Mapping can be used for targeting data table on the different database back-ends. In this simple example, the schema...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah good point. I might have missed that! I’ll look into it soon
Thanks! I confirm it is working.