Skip to content

Conversation

@michal-josef-spacek
Copy link
Contributor

Field storage requirement for JSON column is approximately the same as for a LONGBLOB or LONGTEXT column.

It's defined in
https://dev.mysql.com/doc/refman/8.4/en/storage-requirements.html#data-types-storage-reqs-json

Copy link
Collaborator

@dveeden dveeden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a test for this?

Field storage requirement for JSON column is approximately the same as
for a LONGBLOB or LONGTEXT column.

It's defined in
https://dev.mysql.com/doc/refman/8.4/en/storage-requirements.html#data-types-storage-reqs-json
@michal-josef-spacek michal-josef-spacek force-pushed the add_support_for_json_in_column_info branch from 0dc4cdf to 56473ca Compare April 15, 2025 13:28
@michal-josef-spacek
Copy link
Contributor Author

I am for adding tests later.

There are tests in 40catalog.t for column_info(), but not for column types.
There are tests in 40* for column types, but without column_info().
I am thinking about how to do.

btw: I am preparing a test for JSON type to DBD::MariaDB (michal-josef-spacek/DBD-MariaDB@e849a7a) and I touched this issue. We need to resolve SQL_DBMS_NAME first before the possibility of adding this test in DBD::mysql.

@dveeden dveeden merged commit 8c6c960 into perl5-dbi:master Apr 21, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants