On Thu, 22 Apr 1999, Justin Long wrote:
// It appears that there is a 9k (8,991) limit on queries ... I have
// text files that need to go in TEXT fields that are much longer than
// this. Does anyone have any suggestions as to how to add them to the
// database? Has anyone else encountered this problem?
When I do something like this, I do it in two tables where the
large data is referenced from the other table. For instance, a logging
system I designed for work uses a table called ``events'' that stores
timestamps and other generic event information, then another called
``messages'' that stores the actual textual data. The source of this data
is any random application and some people make *very* verbose event
entries. The way I handle this is to start a transaction, store all of
the event data, then break the message data into 3000 byte chunks, base64
encode it, then store each chunk referencing the id generated from the
event id sequence with an incrementing part number each time. This lets
me store an amount of data on a single message limited only by disk space.
It also means that people using it may start to send movies back as error
messages and all will be well (though it'll be a little painful getting it
into the database).
--
Principal Member Technical Staff, beyond.com The world is watching America,
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L______________________________________________ and America is watching TV. __
