Custom SQL in migrations
TLDR: can I change the SQL in migrations or is that considered bad practice?
Alright, I need some advice. I am still pretty new to Drizzle but I like it a lot so far. The challenge is that I want to use it with SingleStore. It should in general be compatible with MySQL (sauce: https://docs.singlestore.com/cloud/developer-resources/connect-with-application-development-tools/connect-with-node-js/).
They have some time series functionality of course, but I think that can be solved with the magic sql operator. My main concern is that they have custom indexes and table types.
Would it be an option to generate migrations from the CLI, adjust the SQL and work with that? Or is that considered bad practice? If so, I would love to hear how I can approach this.
I would love to hear your ideas, thank you!
Alright, I need some advice. I am still pretty new to Drizzle but I like it a lot so far. The challenge is that I want to use it with SingleStore. It should in general be compatible with MySQL (sauce: https://docs.singlestore.com/cloud/developer-resources/connect-with-application-development-tools/connect-with-node-js/).
They have some time series functionality of course, but I think that can be solved with the magic sql operator. My main concern is that they have custom indexes and table types.
Would it be an option to generate migrations from the CLI, adjust the SQL and work with that? Or is that considered bad practice? If so, I would love to hear how I can approach this.
I would love to hear your ideas, thank you!
