3 people reported

All time, since Aug 28, including 1 thumbs-up on GitHub.

Pull treats two-FK tables as junctions

“drizzle-kit pull appears to classify every table with exactly two foreign-key constraints as a many-to-many junction table.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/drizzle/issues/4969/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Pull treats any table with two foreign keys as a junction. Generated relations replace the table's direct one relations with a many-to-many between the two referenced tables, including self-references.

Is this your bug?

File my report
Where
drizzle-kit pull
Versions
1.0.0-rc.4 to 1.0.0-rc.5
How bad
Breaks a normal workflow.

Not quite your bug?

  1. SQLite table-rebuild migrations delete ON DELETE CASCADE child rows2 people

Original reports2, newest first

  1. drizzle-kit pull treats domain tables with exactly two foreign keys as junction tables#6253
  2. drizzle-kit pull generates a many-to-many whose junction table is one of its own endpoints, and drops the one-relations the foreign keys describe#6197

Do you work on Drizzle?

Claim its RAP Sheet to see what your users report and answer them in one place.