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
Database size increases highly while executing select query [CORE3953] #4286
Comments
Commented by: Alex Kurov (alex.kurov) test base |
Modified by: Alex Kurov (alex.kurov)Attachment: TEST_clear.zip [ 12239 ] |
Commented by: @mrotteveel Might be related to CORE3952 |
Commented by: @hvlad Exactly. |
Commented by: Vladimir Arkhipov (arkinform) We have the same problem with text blobs and the main reason is that we can not use varchar instead of blobs because of limit 32k. |
Commented by: @asfernandes There is no "unlimited" thing in computing. It will be limited by memory, disk or combination of the two. Calling it text, blob or clob changes nothing. So it's a matter of design and implementation requirements and decisions: |
Commented by: Vladimir Arkhipov (arkinform) I think will be usefull 2 options: |
Submitted by: Alex Kurov (alex.kurov)
Is related to CORE3952
Is related to CORE4109
Relate to CORE3951
Attachments:
TEST_clear.zip
Votes: 1
Test base is included
Test query: select (select * from BASE64_ENCODE(photo)) from personphoto
This procedure automates BASE64_ENCODE and it really works with small blobs (<32k), but it test case base size increases 5kk after query execution
The text was updated successfully, but these errors were encountered: