I'm having problems with prisma export

api 💃  master * 👉  prisma export -p ~/dev/blah/api/prisma-export.zip
Downloading nodes !
 ▸    [object Object]

Get in touch if you need help: <https://www.graph.cool/forum>
To get more detailed output, run $ export DEBUG="*"

There is no file generated. And nothing in

.export/

Same problems with the raw export api? https://www.prismagraphql.com/docs/reference/data-import-and-export/data-export-pa0aip3loh/#data-export-using-the-raw-export-api

I tried that but by the time I did I'd already screwed up my database 😕 Still it's only test data. But doesn't fill me full of confidence.

what does it say if you run it with

DEBUG="*"

?

I don't know. I've had to reset docker to attempt to fix that nightmarish 300% CPU use so I'll have to try again when I've reinstalled prisma later

@jof could you export your data directly from your db using SQL?

I guess so. I snapshotted the docker containers so I'll have a go over the weekend and see what works best. I wish Prisma (esp Cloud) was a lot less hand-waving about backups... this stuff should really be built-in to the cli imo.

@jof With Prisma Cloud, the user brings their own database. So they have full control over backup. I'm using AWS RDS so it's doing all of that for me. I'd be interested to see how a restore might work in tandem with prisma

@jof I haven't seen this behaviour before 🙂 If this continues to be an issue, please create a new issue report here: https://github.com/graphcool/prisma

I will, yeah. I plan to spend some time to see if I can repeat the problem.

thanks a lot 😊 I was also going to make the suggestion to do a MySQL dump if you are unexpected problems with

prisma export

.

Slightly on-topic; I hadn't fully looked at Prisma cloud (been using prisma docker until now). I see what you mean about RDS... I should have been paying more attention.

"Slightly on-topic"? 😄