Commit activity
Last 12 weeks · 6 commits
Community health
4 of 6 standards met
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · Last activity 22h ago
See all on GitHub →
What version of are you using? 0.35.3 What version of are you using? 0.26.2 Describe the Bug I have the following in my : As you can see I made a mistake and called both and columns the same name: . Instead of complaining during , it does generate the following .sql: Missing the field, and the is not primaryKey anymore. Which later breaks my when I try to call the field as a foreign key: Not very explicit error, since at this stage, is just supposed to take my for granted! Expected behavior I would have expected the target to fail with an explicit error telling me I used the same key for two distinct columns. I was lucky to catch it at migrate. I could have caught it only in production... Environment & setup Debian 12.
What version of are you using? 0.35.3 What version of are you using? 0.26.2 Describe the Bug I'd like to use in my application side code but have in the database. I have the following When I run for the following schema I get this SQL The issue I'm facing is that the in the generated SQL is in camel case instead of snake case Note: Although the is correct, the selection is wrong Expected behavior I expect the casing to keep the snake case for the view Environment & setup _No response_
Current progress: Optimize multiple calls to multiple checks and one prototype tranversal. Optimize and by caching common string chunks and directly join the chunks instead of using template or .
Recent fixes
[BUG]: db introspection generated schema with invalid syntax for default value with a type castClosedIssue
What version of are you using? ? What version of are you using? ? Describe the Bug From drizzle-kit-mirror repo: https://github.com/drizzle-team/drizzle-kit-mirror/issues/551. For postgres db field: generated schema that fails compilation: I believe it should be: Expected behavior _No response_ Environment & setup _No response_
What version of are you using? ? What version of are you using? ? Describe the Bug From drizzle-kit-mirror repo: https://github.com/drizzle-team/drizzle-kit-mirror/issues/550. in I have: generated with: It fails to compile. I believe the call should be Expected behavior _No response_ Environment & setup _No response_
Report hasn't been filed before. [x] I have verified that the bug I'm about to report hasn't been filed before. What version of are you using? 0.45.2 What version of are you using? 0.31.10 Other packages _No response_ Describe the bug When a table with a column is used in an , drizzle appears to apply the buffer deserialization to the wrong column index in the result row. A value from an integer column (e.g. ) is passed to , which throws: The blob data is stored correctly — returns and the raw bytes are valid. The crash happens during result mapping, not during the query itself. To reproduce Expected behavior The join should return as a and integer columns as numbers, the same way separate selects do. Environment drizzle-orm: (your version) Driver: node:sqlite (DatabaseSync) Node: (your version) OS: macOS Workaround Select from each table separately and join in JS.
Structured data for AI agents
Repository: drizzle-team/drizzle-orm. Description: ORM Stars: 35461, Forks: 1525. Primary language: TypeScript. Languages: TypeScript (98.7%), JavaScript (1.3%). License: Apache-2.0. Homepage: https://orm.drizzle.team Topics: bunjs, mysql, nodejs, orm, postgres, postgresql, sql, sqlite, turso, typescript. Latest release: 0.45.2 (4mo ago). Open PRs: 100, open issues: 1848. Last activity: 22h ago. Community health: 87%. Top contributors: AndriiSherman, dankochetov, L-Mario564, AlexBlokh, Sukairo-02, Angelelz, AleksandrSherman, OleksiiKH0240, RomanNabukhotnyi, realmikesolo and others.