Using DELIMITER function in migration
Hi everyone,
we have been trying to use the DELIMITER function within a prisma migration, but this fails, while the sql executed within mysql workbench was successfully executed.
We also found the following threads:
https://github.com/prisma/prisma/issues/12912 (still open issue, since 2022)
Is there already a solution for this or can there be a fix deployed for that?
GitHub
Support
DELIMITER in migrations · Issue #12912 · prisma/prismaBug description When I use delimiter command in migration file, the migration itself fails because of the invalid syntax. However the syntax is valid and when called from other tools, it works. I s...
5 Replies
You selected to wait for the human sages. They'll share their wisdom soon.
Grab some tea while you wait, or check out
#ask-ai if you'd like a quick chat with the bot anyway!Hey @SHG-TV 👋
Thank you for sharing the link to GitHub Issue.
Do any of the workarounds mentioned in the Issue like this work for you?
GitHub
How to add database functions with DELIMITER · prisma prisma · Disc...
I am trying to add database functions to my mysql database. My first approach was via a seed script which works perfectly fine. But I think the functions do not belong to the seeds and should be in...
Hi @Nurul,
sadly I am dependent on using the delimiter function, so the workarount to try to omit it doesnt work.
we are trying to create a trigger in mysql btw
any updates on this @Nurul (Prisma)
Hey, apologies for the delay in getting back.
I think we need to add support for DELIMETER to allow your use case, I am not aware of any other workarounds at the moment.
Hi @Nurul (Prisma),
thank you very much. Is there an issue for tracking of this or do you have a timeline, when to expect this to be fixed?
Kind regards
Paul