You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
select * from blobz where zin like cast(cast('woord' as char(32766)) as blob sub_type 1) || '!'
works, and returns a set which may or may not be empty, depending on what's in the table.
Now we add one more char:
select * from blobz where zin like cast(cast('woord' as char(32767)) as blob sub_type 1) || '!'
and we get: 335544321 - arithmetic exception, numeric overflow, or string truncation
(in 2.5, the following is added: blob truncation when converting to a string: length limit exceeded)
select * from blobz where zin like cast(cast('woord' as char(32766)) as blob sub_type 1) || '!'
works, and returns a set which may or may not be empty, depending on what's in the table.
Now we add one more char:
select * from blobz where zin like cast(cast('woord' as char(32767)) as blob sub_type 1) || '!'
and we get: 335544321 - arithmetic exception, numeric overflow, or string truncation
(in 2.5, the following is added: blob truncation when converting to a string: length limit exceeded
select * from blobz where zin like cast(cast('woord' as char(32766)) as blob sub_type 1) || '!'
works, and returns a set which may or may not be empty, depending on what's in the table.
Now we add one more char:
select * from blobz where zin like cast(cast('woord' as char(32767)) as blob sub_type 1) || '!'
and we get: 335544321 - arithmetic exception, numeric overflow, or string truncation
(in 2.5, the following is added: blob truncation when converting to a string: length limit exceeded)
Addition: if the BLOBZ.ZIN column is created without any explicit or implicit character set specified (i.e. NONE), then both queries throw: conversion error from string "BLOB". In other words, the second argument cannot be a blob (of any length) in this case.
Submitted by: @paulvink
Is related to QA283
create table blobz (zin blob sub_type 1);
commit;
/* insert stuff - or not... */
The following query:
select * from blobz where zin like cast(cast('woord' as char(32766)) as blob sub_type 1) || '!'
works, and returns a set which may or may not be empty, depending on what's in the table.
Now we add one more char:
select * from blobz where zin like cast(cast('woord' as char(32767)) as blob sub_type 1) || '!'
and we get: 335544321 - arithmetic exception, numeric overflow, or string truncation
(in 2.5, the following is added: blob truncation when converting to a string: length limit exceeded)
This happens with LIKE, STARTING and CONTAINING.
Commits: aafa381 1fc093e 3447e70 7e182bc a82fbb6 55f5ce3
The text was updated successfully, but these errors were encountered: