How to increase text editor max chars length- (Max 65535 characters)

[expired user #8645]'s profile image [expired user #8645] posted 9 years ago in General Permalink
I have a text data type coulumn (sqlserver) in one of the table.The content length is nearly 100000 characters. I was trying to make changes to the content in HeidiSql-Texteditor.It's not allowing me to make changes and it's saying 65535 characters (Max 65535). Is there a way to increase this size...?
Code modification/commit from ansgar.becker, 9 years ago, revision 4905
TEXT data type has a maximum length of 65k for MySQL only. Introduce other values for MSSQL and PostgreSQL. See http://www.heidisql.com/forum.php?t=17747
ansgar's profile image ansgar posted 9 years ago Permalink
The maximum length is set by a detection routine which returned values from the TEXT data type in MySQL, which is 65k. In r4905, this is fixed for MSSQL and PostgreSQL, which allow more text here.
[expired user #8645]'s profile image [expired user #8645] posted 9 years ago Permalink
But, The max length of the text data type in Sqlserver is not 65535. I'm able to see full data in the editor but I can't add more characters. It's allowing to delete content.

https://msdn.microsoft.com/en-us/library/ms187993(v=sql.100).aspx
ansgar's profile image ansgar posted 9 years ago Permalink
Yes, that's what I meant. r4905 fixes that limitation in the text editor. You just need to update to the latest build (Help > Check for updates)
[expired user #8667]'s profile image [expired user #8667] posted 9 years ago Permalink
hello, may be i doing something wrong, but in build 4905,

in PostgreSQL
text editor showing me only 255 characters on field with type "TEXT"

thanks
1 attachment(s):
  • screen
ansgar's profile image ansgar posted 9 years ago Permalink
As stated here, PostgreSQL's "TEXT" data type supports "unlimited" (!) text length :)

Let me check what HeidiSQL detects there. Surely some glitch in my detection logic.
Code modification/commit from ansgarbecker, 9 years ago, revision 4922
SUBSTR() in PostgreSQL seems 1-based, not 0-based. Fixes non-working TDBQuery.EnsureFullRow and TDBQuery.HasFullData. See http://www.heidisql.com/forum.php?t=17747
ansgar's profile image ansgar posted 9 years ago Permalink
Should be fixed in r4922. Please update and test yourself. For me it fixes the issue.

SUBSTR() seems to be 1-based, not 0-based, in PostgreSQL. I had assumed 0-based and so the partial content did not have 256 characters but 255, and so the "load-full-row" logic did not detect it as incomplete.
[expired user #8667]'s profile image [expired user #8667] posted 9 years ago Permalink
Hi,

it seems we have new strange problem (after upgrading from 4905 to 4922)
i can't see no any data - because "sql query" has few errors

thanks!
1 attachment(s):
[expired user #8667]'s profile image [expired user #8667] posted 9 years ago Permalink
this screen
1 attachment(s):
  • heidi_error
ansgar's profile image ansgar posted 9 years ago Permalink
This is an error due to a recently modified query for getting table indexes.
Here's the forum thread for that topic. Let's discuss that there.
Code modification/commit from ansgarbecker, 9 years ago, revision 4925
Attempt to fix query for detecting table indexes on PostgreSQL. See http://www.heidisql.com/forum.php?t=17747
ansgar's profile image ansgar posted 9 years ago Permalink
Just try out r4925.
[expired user #8667]'s profile image [expired user #8667] posted 9 years ago Permalink
thank you, it's works :)

Please login to leave a reply, or register at first.