We ended up having to go with MySQL on heroku in o...
# orm-help
t
We ended up having to go with MySQL on heroku in order to get around the performance problems we were having. We couldn’t migrate our graphcool data to Postgres with inline tables, but we have been able to with MySQL. So we’ll need to figure out how to deploy to the ClearDB addon with Heroku. @Harshit is there any sort of guidance you could provide here?
h
That is kind of expected as GraphCool also used MySQL under the hood. What I will suggest here if you can, wait for Prisma 2 general release.
t
@Harshit We can’t really afford to wait, we are pretty much good to launch other than the DB, and need to start using the new server code that’s ported over to the new prisma syntax. The longer we wait to launch, the longer we have to keep both the graphcool version of the code and the prisma version of the code in sync which would end up being a pretty big pain. So are you saying that it currently wouldn’t even be possible? Or just that there isn’t any tutorials or examples of anyone having done that before and that it would be difficult to do? Would waiting for Prisma 2 make it easier to deploy to ClearDB somehow?
h
I guess you are fine with Prisma 1 and MySQL then. We will continue to give bug fixes to Prisma 1. Just suggest the above if you had time. Otherwise just upgrade to Prisma 1.
t
K well I’m just moving to EC2 for prisma/mysql because I don’t think ClearDB is possible on Heroku right now