New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Cannot use a Buf as a string" when selecting MySQL TEXT col #110
Comments
|
Hi, In the meantime you probably want to use |
|
That works, thanks. The example files in the repository (ie: examples/mysql.pl6) should probably be updated to use that syntax instead of fetchrow (or ideally show examples for each of the available methods with documented pros/cons for each). |
|
Can we just tag fetch_* to DEPRECATED? Or are there still use case that
need it?
2017-12-15 10:43 GMT+01:00 Jonathan Stowe <notifications@github.com>:
… Hi,
Yes the fetch* methods do indeed attempt to stringify the column data
which is always going to be problematic with TEXT or BLOB columns, I
*think* the beahaviour should be that it leaves it as-is and makes a
warning recommending you to use .roiw instead, but I'd like to get some
other opinion on that before making the change unitlaterally.
In the meantime you probably want to use .row instead, it has the added
advantage of returning properly typed data rather than Str for all columns.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#110 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMYVfx61Jr3k0i2qVNJ3ghlYNvIBQJ89ks5tAj88gaJpZM4RC9dj>
.
--
Sylvain "Skarsnik" Colinet
Victory was near but the power of the ring couldn't be undone
|
|
Yes, I think that DEPRECATE those are the way to go.
…On Fri, Dec 15, 2017 at 2:21 PM, Skarsnik ***@***.***> wrote:
Can we just tag fetch_* to DEPRECATED? Or are there still use case that
need it?
2017-12-15 10:43 GMT+01:00 Jonathan Stowe ***@***.***>:
> Hi,
> Yes the fetch* methods do indeed attempt to stringify the column data
> which is always going to be problematic with TEXT or BLOB columns, I
> *think* the beahaviour should be that it leaves it as-is and makes a
> warning recommending you to use .roiw instead, but I'd like to get some
> other opinion on that before making the change unitlaterally.
>
> In the meantime you probably want to use .row instead, it has the added
> advantage of returning properly typed data rather than Str for all
columns.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#110 (comment)>, or
mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
AMYVfx61Jr3k0i2qVNJ3ghlYNvIBQJ89ks5tAj88gaJpZM4RC9dj>
> .
>
--
Sylvain "Skarsnik" Colinet
Victory was near but the power of the ring couldn't be undone
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#110 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AI8runBgTrdjtd48qXFtZMkbjgqiBFTbks5tAtTYgaJpZM4RC9dj>
.
--
Salvador Ortiz García
Director General
Matías Software Group, S.A. de C.V.
Tel: 55 6391-2249
|
|
I'll try and take a look at fixing the examples and adding a deprecation tomorrow. |
Initially discussed in #110. The README indicates they should be removed in June 2022, which is fairly generous. Legacy tests have been converted to use the newer functions (allrows or row), or removed when functionality was duplicated.
Initially discussed in #110. The README indicates they should be removed in June 2022, which is fairly generous. Legacy tests have been converted to use the newer functions (allrows or row), or removed when functionality was duplicated.
Attempting to retrieve the value of a TEXT type column from a MySQL database is throwing an error. I can avoid the error for now by not selecting that column, or by changing it to a different datatype (ie: VARCHAR).
The text was updated successfully, but these errors were encountered: