#48 [Feat]: Render columns based on column size instead of only types

[Anonymous]

Originally created by: robinbertram
Originally owned by: debba

Prerequisites

• [x] I have written a descriptive issue title
• [x] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

We store UUIDv4 AS VARBINARY(36) and this update (https://github.com/debba/tabularis/issues/36) broke the table view for me.

This is the same table from TablePlus (and it used to look the same in Tabularis):

Would it be possible to use the length/size of the column to decide how to render the data? If it's smaller than X bytes, then render, like before.

Motivation

Even varchars can be very large, up to 65,535 bytes:

Values in VARCHAR columns are variable-length strings. The length can be specified as a value from 0 to 65,535.
(https://dev.mysql.com/doc/refman/9.3/en/char.html)

So only using the type of column might not be enough anyway?

Example

No response

[Anonymous]

Originally posted by: debba

It should be fixed with this commit: https://github.com/debba/tabularis/commit/c6f5c7594989a6f457f284702da038e7c6df12ef

Wll be online in next release

[Anonymous]

Ticket changed by: debba

• status: open --> closed

[Anonymous]

Originally posted by: robinbertram

Hi again @debba!

I updated to the new version today. Now it looks like this:

It recognizes text/plain instead of application/octet-stream but is not really the view I was hoping for :/

If you wanna give it a go you can try this:

MySQL 8.4

CREATE TABLE `test_uuidv4` (
  `id` int NOT NULL AUTO_INCREMENT,
  `uuid` varbinary(36) NOT NULL,
  `created_at` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `updated_at` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  UNIQUE KEY `uuid` (`uuid`)
) ENGINE=InnoDB AUTO_INCREMENT=0 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_swedish_ci;

INSERT INTO test_uuidv4 (uuid)
VALUES 
    ('f5866cd4-30bf-4806-9f9a-9508abb72c9f'),
    ('17171660-3acd-44a4-a89f-51af9eeecb50'),
    ('fb107026-b393-4062-8768-f6a7868478b9');

[Anonymous]

Originally posted by: debba

Tested now, but it looks ok.
Are you sure you are in the latest version?

[Anonymous]

Originally posted by: robinbertram

I'm running v.0.9.4 on Ubuntu 25.10.

[Anonymous]

Originally posted by: robinbertram

[Anonymous]

• assigned_to: debba

[Anonymous]

Ticket changed by: debba

• status: closed --> open

[Anonymous]

Originally posted by: debba

@robinbertram are you able to debug direcly by code?
tha'ts a very weird situation.