Replies: 1 comment
-
I've raised a bug report, #3183 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to reference a table from another schema in a foreign key constraint. I'm doing this by defining the external table with the following schema definition and then referencing the table in my foreign key constraint. This is working.
This external table should not be managed by Drizzle and should not be included in any migration script. However, when I run drizzle-kit generate it is.
Apparently, there is an implicit default Drizzle config
schemaFilter
value ofpublic
, but that didn't stop theauth.users
table from being included in the migration file. I tried to explicitly set theschemaFilter
config property to["public"]
, but that still did not stop that table from being included in the migration script. What am I missing? Without this filter working how else can I define a foreign key constraint with an unmanaged table? ThanksBeta Was this translation helpful? Give feedback.
All reactions