LogoLogo
codatum.comSign InStart for free
  • Introduction
  • Getting Started
    • Quick Start
    • Concept (Further reading)
      • Why did we a choose Block Editor over Cell-based Editor?
  • Connect and Manage Data
    • Connection
      • Sync Table Metadata
    • Supported Warehouses
      • BigQuery
      • Snowflake
      • Other Warehouses
    • Catalog
    • Search
  • Data Exploration
    • Data Exploration Overview
    • Notebook
      • Doc Page
      • Grid Page
      • SQL Block
      • Version
      • Notebook FAQ
    • Chart
    • Explorer
    • Parameter
    • (Appendix) Cache
  • AI Assist
    • SQL Assistant
  • Sharing
    • Sharing Overview
    • Teamspace
    • Shared Notebook
    • Report
    • Public Link
    • Signed Embed
      • How to Set Up Signed Embed
  • Account Management
    • Account
    • Account Settings
  • Workspace & User Management
    • Workspace
  • User Management
    • Invitation
    • Group
  • Security
    • Security Overview
  • Audit logs
  • IP Access Control
  • Access control
    • Access Control Overview
    • Access Control for Workspace
    • Access Control for Resources
      • Access Control for Group
      • Access Control for Teamspace
      • Access Control for Notebook
      • Access Control for Connection
      • Access Control for Report
  • [Under Construction] Plan and Billing
    • Limit and usage
    • Downgrade and cancel
  • Best Practices
    • Advanced Control Structures in SQL
  • Other considerations
    • System requirements
Powered by GitBook

Reference

  • Privacy policy
  • Terms of service
  • JP Docs Site
On this page
  • Key Features
  • Parameter Handling:
  • SQL Result Cache Handling:
  • Frequency of Automatic Snapshots

Was this helpful?

  1. Data Exploration
  2. Notebook

Version

Save and restore analysis states automatically and manually

Versions can be saved and restored automatically or manually. If your data becomes corrupted or you need to revert to a previous state, you can restore it from a saved version.

Key Features

  • Automatic Versions:

    • Automatically create versions when changes are made or after a certain time.

    • Old versions are automatically deleted to save space.

  • Manual Named Versions:

    • Manually create versions and give them names.

    • Manually created versions are maintained separately and are not overwritten by automatic versions.

  • Restore Notebook:

    • Create a new notebook from a version (existing notebooks cannot be overwritten).

  • User-specific Parameters:

    • In a Notebook, parameter values and their linked execution results are shared among multiple users. However, in a Version, these can be held individually by each user.

    • This can also be realized in Reports.

Parameter Handling:

Parameter values can be specified as URL parameters. By changing the shared URL, you can modify the default inserted values. This enables you to reproduce the execution results of past SQL with specific parameters.

SQL Result Cache Handling:

As long as the SQL Block Cache has not expired, you can access SQL execution results and charts. Even after losing the SQL Block Cache, you can re-execute the SQL Blocks in the snapshot, which will update the execution results and charts.

Frequency of Automatic Snapshots

Changes are not saved as individual snapshots for every edit. Instead, multiple changes are grouped together and saved in a single snapshot. Typically, changes made over a certain period, such as an hour, are saved together.

PreviousSQL BlockNextNotebook FAQ

Last updated 7 months ago

Was this helpful?