Skip to content
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

Bug: export only exports the first table, even when all are selected #630

Open
2 tasks done
Icaruk opened this issue Dec 19, 2024 · 3 comments
Open
2 tasks done

Bug: export only exports the first table, even when all are selected #630

Icaruk opened this issue Dec 19, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Icaruk
Copy link

Icaruk commented Dec 19, 2024

Describe the bug

Export only exports the first table, even when all are selected.

Steps to reproduce

  • Connect to my cloud instance (it happened on my self hosted instance too)

  • Explorer tab

  • Export database
    image

  • Output file is like this:

-- ------------------------------
-- OPTION
-- ------------------------------

OPTION IMPORT;

-- ------------------------------
-- USERS
-- ------------------------------

DEFINE USER REDACTED ON DATABASE PASSHASH 'REDACTED' ROLES OWNER DURATION FOR TOKEN 1h, FOR SESSION NONE;

-- ------------------------------
-- PARAMS
-- ------------------------------

DEFINE PARAM $version VALUE 2 PERMISSIONS FULL;

-- ------------------------------
-- TABLE: table1
-- ------------------------------

DEFINE TABLE table1 TYPE ANY SCHEMAFULL PERMISSIONS FULL;

DEFINE FIELD in ON table1 TYPE record<user> PERMISSIONS FULL;
DEFINE FIELD out ON table1 TYPE record<crew> PERMISSIONS FULL;
DEFINE FIELD role ON table1 TYPE record<crewRoles> PERMISSIONS FULL;



-- ------------------------------
-- TABLE DATA: table1
-- ------------------------------

Using surreal export command outputs the right file.

Expected behaviour

All tables are exported

Surrealist Environment

Version: 3.1.7
Flags: feature_flags: false, query_view: true, explorer_view: true, graphql_view: true, designer_view: true, auth_view: true, functions_view: true, models_view: true, apidocs_view: true, themes: true, syntax_themes: false, newsfeed: true, database_version_check: true, highlight_tool: false, legacy_serve: false, cloud_enabled: true, cloud_endpoints: production, cloud_access: true, cloud_killswitch: true, changelog: auto

Contact Details

[email protected]

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Icaruk Icaruk added bug Something isn't working triage This issue is new labels Dec 19, 2024
@macjuul macjuul removed the triage This issue is new label Dec 20, 2024
@macjuul
Copy link
Contributor

macjuul commented Dec 20, 2024

Hey! I can indeed reproduce this issue. Interestingly enough it appears to be caused by the "Include versions" checkbox, and disabling it resolves it for me. You can use this as a temporary workaround until we resolve the issue entirely

@Icaruk
Copy link
Author

Icaruk commented Dec 20, 2024

Hey! I can indeed reproduce this issue. Interestingly enough it appears to be caused by the "Include versions" checkbox, and disabling it resolves it for me. You can use this as a temporary workaround until we resolve the issue entirely

Thanks for the workaround!
Whats does this option do?

@macjuul
Copy link
Contributor

macjuul commented Dec 20, 2024

The version checkbox is used by SurrealKV backed databases to signal the inclusion of exporting historic data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants