I hit up against something like this a while ago,
but I didnt have time to debug so I used a quick hack to
get by.
Say you are storing a text article
--------------------------
| ArticleID | INT |
--------------------------
|ArticleName | TEXT |
--------------------------
I just created a separate table to hold the text
-------------------------
Articleid | INT |
-------------------------
textid | INT |
-------------------------
text | TEXT |
-------------------------
When saving the text I split it up into small chuncks
and then give each chuck an number in order.
Each chunck gets stored in the second table
and is identified by the articleid.
To reassemble the text I read in all the chunks from teh
second table.
The my program works with the text
When I need to save the edited text I drop all entries for
that article from the second table , break the edited text into
chunks again. And save.
Its probably inefficent as hell, but for my purposes it worked.
-----Original Message-----
From: Dougherty, Sean [mailto:[EMAIL PROTECTED]]
Sent: 10 July 2001 13:45
To: '[EMAIL PROTECTED]'
Subject: String Size Limit?
I'm running into an odd string size limitation. I've traced it down as far
as I can get, and I didn't run across anything in the docs or on any
searches I've run so I figured I'd try here. The field in the database is a
TEXT type column. I'm appending to the front of the text field each time
using:
UPDATE field SET notes=CONCAT("newtext",notes) WHERE ...
However the field is cutting off after 4096 bytes. With a hunch that CONCAT
may have been causing the limit, I switched to doing the concatenation
inside of the application and setting the full field. The same cut-off
occurs in storage, however the SQL executes correctly so it's not like the
query is getting cut off and not seeing the WHERE clause.
Seeing as this happens in CONCAT which should be server side I suspect I'm
running into a server-side limitation. My app is PHP3 over IIS on NT4.0
using MyODBC 2.50.3300 to a Linux Server running MySQL 3.22.32 precompiled
(when you get 100 day 24/7 uptime no problem you don't upgrade!). What
incredibly obvious piece of documentation am I missing, is this a "you need
to upgrade thing", or what would be a reasonable work-around in this rather
abstracted environment?
Thanks,
Sean
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
