Boian Ivanov
DTDrizzle Team
•Created by Boian Ivanov on 9/22/2023 in #help
[BUG] Multi schema tables with same name
Let's hope you're right and they do open source it soon enough 🤞
Thank you for the info though 👌
17 replies
DTDrizzle Team
•Created by Boian Ivanov on 9/22/2023 in #help
[BUG] Multi schema tables with same name
As I've been on the lookout of how this can be fixed, I've stumbled upon the fact that this is caused by the "drizzle-kit" package which is not OSS, which makes it even harder when trying to figure out how this issue can be resolved. From what I can see initially from the transpiled .cjs file it seems that the schema passthrough on generation at some point doesn't reach the full extend of the
it reference, but it's quite hard to understand when the source is not publicly available :/17 replies
DTDrizzle Team
•Created by Boian Ivanov on 9/22/2023 in #help
[BUG] Multi schema tables with same name
Yes, we've tried working around it, but it's quite hard, especially when the design of the database requires same names. Are there any potential ideas on where the bug may be, as I might be able to try and fix it
17 replies
DTDrizzle Team
•Created by Boian Ivanov on 9/22/2023 in #help
[BUG] Multi schema tables with same name
I’ve even tried having the non schema tables in a root schema hoping that there won’t be a conflict, but as the schemas are not taken into account, the migrations are still using the one table that’s defined last in the schema
17 replies
DTDrizzle Team
•Created by Boian Ivanov on 9/22/2023 in #help
[BUG] Multi schema tables with same name
Yes, this is exactly the way we’ve done this. Even if table A is in the public schema (no schema) and table B is in a schema, as long as they have the same exact name, drizzle is confused, so it looks like it’s not taking into account the schema choice when generating the migrations and the last table is overwriting the first one. The only way around this is for the names to not conflict, which might not be ideal depending on use case
17 replies
DTDrizzle Team
•Created by Mohammed Anas on 8/10/2023 in #help
Aws Rds with drizzle
Tell that to my manager 🤣
22 replies
DTDrizzle Team
•Created by Mohammed Anas on 8/10/2023 in #help
Aws Rds with drizzle
Assuming you're not on v1 due to the need for the data-api
22 replies
DTDrizzle Team
•Created by Mohammed Anas on 8/10/2023 in #help
Aws Rds with drizzle
The issue is if you need to use Aurora Serverless on RDS, then the only option is via the data-api client and via drizzle it has its limitations
22 replies
DTDrizzle Team
•Created by Noahh on 8/23/2023 in #help
Missing @opentelemetry/api module at runtime when upgrading to 0.28.4
I also had this issue this morning, but the
drizzle-orm@types-bugs tag fixed it 🎉55 replies
DTDrizzle Team
•Created by Mohammed Anas on 8/10/2023 in #help
Aws Rds with drizzle
Well that's great I suppose, but I cannot get anyone else to review it so we can move it forward 😢
22 replies
DTDrizzle Team
•Created by Mohammed Anas on 8/10/2023 in #help
Aws Rds with drizzle
@fustilio. unfortunately my PR fixes the mapping for raw sql queries. It basically guaranties your return types to be as per the select and not as the aws-sdk would return them
22 replies
DTDrizzle Team
•Created by Boian Ivanov on 8/17/2023 in #help
Issue with diverging responses via RDS Wrapper on rawSQL query.
I have raised a PR for the aforementioned issue here, it would be great to hear some feedback on what we can improve upon so it can hopefully be an addition to the main package
3 replies
DTDrizzle Team
•Created by Boian Ivanov on 8/17/2023 in #help
Issue with diverging responses via RDS Wrapper on rawSQL query.
We're currently considering the following client that maps the results to a more manageable format. Maybe their formatting implementation could be used for the Drizzle RDS client
3 replies