< satire>
Hi!!!!! I have data on several 1000s multi-generation family trees stored in a MySQL database.
To faciltate a simple schema, I opted for a pretty novel representation:
I store each tree *graphically* in gif files, concatentate
all the gifs into one big binary object, and then store the huge resulting
data in a one row, one field table. It is working pretty well so far,
but I am seeking the wisdom of the Monks on how to
update the structure when a couple with children *divorce* then *remarry* other
people. (No modules, please: prefer to code
everything myself.) Thanks in advance!!!!!
</satire>
Sigh. I'm not bashing the anonymous monk who posted; rather,
expressing my amazement at the staggering ways folks
(mis)use databases.
<satire>
Your problem is the use of the GIF format for your data. If you really want to move the cutting edge of image-based storage of text-data, I suggest
PNG
</satire>