This repository has been archived by the owner on Oct 10, 2022. It is now read-only.
Duplicate tables across schema are incorrectly generated #208
Labels
enhancement
new feature or bug with easy workaround
Assume the following DB setup:
Running the following command:
will result in the 3 output files:
user
,migration
, andcategory
. The problem is that themigration
file is being updated and columns appended instead of a new file being generated. So the output file will have something like the following:even though there is a single
id
column in either table.My initial issue was similar to #144 but just generating the files from all the schema has the above mentioned downside. I could rename all my tables to be unique.
I'd propose adding a way to exclude tables from being generated (or entire schema from being generated). That way the other schema could be included in generation (in my case for cross schema foreign keys) and the duplicate models wouldn't be an issue.
Another proposal would be to create an output folder for each schema. That was all tables are unique in their folders. This is similar to #204.
Let me know if there is anything I can do to help!
The text was updated successfully, but these errors were encountered: