Results grid

A results gridthat reads your data.

Every value in the results grid draws by its DynamoDB type, in your editor theme's colors. Numbers line up on the right, entity keys read piece by piece, timestamps read as dates, the TTL column says how long an item has left, and sets show as chips that fit the column.

Keys read piece by piece. When a key cell matches the template inferred for one of the table's entities, each piece takes its own color: the entity name, the markers inside it, and the values between them, with the delimiters muted. Narrow the column and each piece truncates on its own, so the shape of the key survives. The partition key carries a # and the sort key a ⇄, and the lock sits in the header's corner so every title starts in the same place. See how entities are inferred →

Sets look like sets. A string, number, or binary set shows its members as chips behind a small SS, NS, or BS tag, and a list of one scalar type does the same behind an L. How many chips show is measured against the column, so narrowing it shows fewer chips and a larger count. Binary shows a B tag with both ends of its base64, and a map reads as inline JSON with keys, values, and punctuation each in their own color. See the editor for every type →

Dates edit as dates. Expiries edit as time. A column the schema registry reads as timestamps shows the date, then the clock in muted text at the precision it was stored with. Its editor has a precision control, a month calendar, and time fields, and it writes back in the same format. On a table with TTL turned on, the expiry column carries a green TTL badge and says how far off it is, and its editor names the moment as a date and time, a duration with quick chips, or raw Unix seconds. Every save stages as a pending change. See pending changes →

Two items, side by side. Select two rows and choose Compare 2 items. Both are read fresh from the table by key and lined up attribute by attribute, keys first, with each difference marked Differs, Only in A, or Only in B. Values compare by type, so 1.50 and 1.5 match. Turn on Only differences to hide the rest. An arrow copies a value across and stages it as a pending change, and key attributes never copy. See pending changes →

Cell by cell

01Plain strings stay plain

A top-level string reads in the normal text color with no quotes. The theme's string color is kept for chips and inline JSON, where it marks a value out.

02Numbers on the right

Numbers right-align in tabular numerals and show the digits DynamoDB stored, never reformatted.

03Your theme's colors

Cell colors come from the editor theme picked in Settings and change live when it does, including a switch between light and dark.

04TTL at a glance

The expiry column reads in 8d or in 116d, today in the alert color, or expired, and only on a table with TTL turned on. Hover shows the stored seconds.

05Dates at their precision

A date-only value shows no clock. A stored time shows to the minute, second, or millisecond it was written with, in your own timezone.

06Nothing rewritten on disk

Display is display only. Sorting, filtering, and every save use the stored value, and the raw value is always on hover.

Read by typeEvery DynamoDB type draws its own way.
Keys by segmentEntity keys colored piece by piece.
Chips that fitMeasured against the column, not a fixed count.
Time as timeDate and TTL editors that keep the stored format.

Every value,read the way it is stored.