Inline table Preview

An inline table is a small table stored in a notebook. You can edit its values directly and join them with connection data from a SQL block.

INFO

This feature is in preview. To request access, contact Codatum support.

Creating and editing an inline table

You need edit permission on the notebook.

Creating an inline table by entering CSV

1. In Inline tables in the left sidebar, open Add, then select Create new under Inline table.
2. Enter values in CSV format and select a data type for each column.
3. Select Save.

Creating an inline table from a CSV file

1. In Inline tables in the left sidebar, open Add, then select Upload CSV under Inline table.
2. Select a UTF-8 CSV file.

Creating an inline table from a query result

You can save the result of a SQL block as an inline table. Referencing it from SQL on another connection lets you join data across connections. You need execute permission on the connection.

1. Run SQL in a SQL block.
2. Select the Save as inline table icon at the top right of the SQL block. You can't select it until you run the SQL.
3. Enter a name.
4. Turn on Link to this SQL block to re-run this block later with refresh. When it's off, the inline table keeps only a copy of the result.
5. Select Save.

When you save with Link to this SQL block turned on, the inline table name appears at the top right of the SQL block, and you can select it to open the editor. To save again from a linked block, open the SQL block menu and select Save as inline table.

You can save results with up to 2,000 rows. You can't save results that contain columns whose types aren't supported as inline table data types, such as ARRAY or STRUCT. Cast them in the SQL to save the result.

An inline table belongs to its notebook. You can change its name and content from the inline table editor.

Creating an inline table with the AI agent

You can ask the AI agent to create inline tables from the chat. It can also save a tool result from an agent connector directly as an inline table, without pasting the data back into the chat.

• When the agent saves a tool result, the result JSON is converted into a table, and column data types are inferred from the values.
• Inline tables saved by the AI agent aren't linked to a SQL block, so you can't refresh them.

Refreshing an inline table

For an inline table saved with Link to this SQL block turned on, you can update its data by re-running the linked SQL block. To change the query, edit the linked SQL block.

To go to the linked SQL block, select the Go to the linked SQL block icon in the Inline tables list in the left sidebar, or select the block name shown in the inline table editor.

1. Open the inline table editor.
2. Select Refresh.

Refresh runs with the following specification:

• SQL runs with the permissions of the user who refreshed. You need execute permission on the connection.
• SQL always runs again without using cached results.
• If the SQL uses parameters, they're resolved with the values saved on the page.
• The result is saved as a new revision.

If the linked SQL block was deleted or the SQL fails, the refresh fails and the inline table content doesn't change. You can't refresh when the linked SQL block references this inline table itself.

Revisions

Each time you save or refresh an inline table, its content at that point is recorded as a revision. You can revert to a past revision as follows:

1. Open the menu in the inline table editor, then select Revision history.
2. Select Revert to this revision on the revision you want to restore.

Reverting saves the content of the selected revision as a new revision. Later revisions aren't deleted by reverting.

Old revisions that aren't referenced from anywhere might be deleted automatically. The 5 most recent revisions of each inline table and revisions referenced from versions and other resources are retained.

Referencing an inline table from SQL

Enter /inline-table/ in a SQL block and select an inline table. Inline tables are supported in SQL for BigQuery, Snowflake, Databricks, and Redshift.

Select an inline table reference to change its Alias. Turn off Assign alias to the end to use an AS clause entered directly in the SQL.

Inline table values are included in the SQL sent for execution. The values might also appear in query history for the connection.

Deleting an inline table doesn't remove its references from SQL blocks. A reference to a deleted inline table becomes unresolved, and you can't run that SQL.

Data types and values

You can select one of the following data types for each column. You can't save CSV that contains values that don't match the format.

Data type	Value format
STRING	Any string.
INTEGER	Integer within the 64-bit integer range, e.g. -42.
FLOAT	Number, including exponent notation, e.g. 3.14 or 1e-3.
BOOLEAN	true or false (lowercase).
DATE	YYYY-MM-DD, e.g. 2026-08-25.
DATETIME	YYYY-MM-DDTHH:MM:SS with up to 6 fractional second digits, e.g. 2026-08-25T13:45:00.
TIMESTAMP	Datetime with Z or ±HH:MM, e.g. 2026-08-25T13:45:00+09:00.

An unquoted empty field is treated as NULL. A quoted empty string ("") is valid as an empty string for STRING, and invalid for the other data types.

Versions

Inline tables are included in versions. See the version specification for behavior when you inspect, restore, or create a notebook from a version.

Constraints

• An inline table name can contain up to 200 characters, and an alias can contain up to 128 characters.
• CSV must use UTF-8 and include a header row.
• An inline table can contain up to 100 columns and 10MiB.
• SQL can reference inline tables with up to 2,000 rows. You can save an inline table that exceeds 2,000 rows, but you can't run SQL that references it.
• You can save query results with up to 2,000 rows as an inline table.
• A notebook can contain up to 100 inline tables.
• A notebook can retain up to 1,000 inline table revisions with a combined size of 1GiB.
• SQL, including expanded inline tables, can be up to 900KiB.
• Redshift can't reference inline tables whose values contain control characters other than tabs, line breaks, and a few others.
• You can't import or export a notebook that contains inline tables as a file.
• Table and Query result in dynamic options can't reference inline tables.
• Deleting an inline table reduces the inline table count usage. Revision count and storage usage are released later, so a revision quota can remain exceeded immediately after deletion.

See also the numeric limits.