Drizzle kit drops and re-adds constraint
It appears that drizzle kit attempts to drop my constraints and then re-add them. The difference this time is it add the schema "public" to the tables when constructing the constraints.
Is this normal? This only happens in drizzle-kit@beta (0.20.10-8c690cf). I have to upgrade to drizzle-kit@beta to avoid the schema files malformed error (https://github.com/drizzle-team/drizzle-orm/issues/1554)
GitHub
[BUG]: how to recover from snapshot.json data is malformed · Issue ...
What version of drizzle-orm are you using? latest What version of drizzle-kit are you using? latest Describe the Bug When trying drizzle-kit generate:sqlite --config drizzle.config.ts I get drizzle...
1 Reply
I understand that if a schema is not specified, the default one is public, so what's the point of forcing "public" namespace for constraint like this? It would make the migration files huge