Михаил

Test case for `text` affinity for `bytea` column. SQLite table ```sql CREATE TABLE "BLOB" ( i INTEGER PRIMARY KEY AUTOINCREMENT, b BLOB ); ``` PostgreSQL foreign table ```sql CREATE FOREIGN...

For not ugly data for `bytea` there is solution draft near https://github.com/mkgrgis/sqlite_fdw/blob/f109f0facf3b85da6b57abb0b7c5b64773997f27/sqlite_query.c#L109

Look like we need `CAST` in conditions for `bytea` columns of foreign tables. Depends on affinity, data is from first example ```sql SELECT i, b, typeof (b) FROM "BLOB" where...

Now for PostgreSQL with `select * from "blob" where b = 'テスト';` there is base query `デバッグ: sqlite_fdw: finalize SELECT `i`, `b` FROM main."blob" WHERE ((`b` = X'e38386e382b9e38388'))` only 1...

> To support it, we need to define the conversion specification for various patterns of combinations of types between PostgreSQL and SQLite. @t-kataym , what about https://github.com/mkgrgis/sqlite_fdw/tree/readme-fix-and-additions#datatypes ?

> > what about https://github.com/mkgrgis/sqlite_fdw/tree/readme-fix-and-additions#datatypes ? > @mkgrgis Thank you for summarizing it. Please give us a time to confirm it. Yes, please. There is updated table now. I understand...

> Anyway, I believe that you understood what I wanted to say. Yes, @t-kataym . Let's study about SQL:2016 behaviour in context of prefetched `SELECT col1 FROM tbl` for `SELECT...

Hello, @nxhai98! What about we are discussing? There are 3 aspects of transformation table - as is (current implementation) - ISO SQL:2016 (recommendations) - *future behaviour* and also there are...

_About SQLite BLOB transparent_ > As you can see, the error just because the text presentation is not match with target type. Not only presentation, @nxhai98, but also **encoding**! Please...

> Thank for explaining. However, SQLite INT/REAL => bytea still 'x' in the datatype table. Could you update this. Yes, fixed, @nxhai98! > Currently, sqlite_fdw support only utf-8 SQLite database...