New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SurrealQL statements for backup/restore and import/export #30
Comments
I was just about to add a feature request for this until I hit the checkbox labeled "I have searched the existing issues"! |
EDIT: See comment below for a much better way I couldn't wait any longer for this feature so I just rolled my own! |
@tobiemh Sorry to ping you on this, but just wanted to make sure this feature request is not forgotten! I use Google's firebase functions to automatically make backups of my database to firebase storage (with a custom backup script that basically loops through all the records in my database - not great performance-wise but is fine for my use-case). Since they are run from a node environment it sure would be useful if I could actually retrieve the export file via the JavaScript library. I suppose this would be useful for others too who are looking for similar functionality? Or maybe @kearfy would be the one to ask about the js library? Thanks! |
Silly me - this functionality is already possible for me using the /export and /import REST endpoints! Not sure why I didn't think of this before. |
Is your feature request related to a problem?
Currently we can only perform Backup/Restore and Import/Export with CLI and There is no way to initiate these task with SurrealQL.
Describe the solution
I suggest adding SurrealQL statements for performing backup/restore and import/export data.
Reference: https://www.cockroachlabs.com/docs/stable/backup.html
These statements will enable us to initiate and schedule backup/restore from code.
Alternative methods
CLI can be used to perform backup/restore.
SurrealDB version
v1.0.0-beta.4
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: