http://qs321.pair.com?node_id=106858


in reply to FreezeThaw Problem

You have given us rather little information about what your logic looks like. For instance FreezeThaw has various hooks to allow you to put logic in the freezing and thawing process. Are you using those? If not, then I would suggest giving Storable a shot.

However I would wonder whether your frozen string is getting long enough to not fit in whatever database field it is going into. Check whether that is plausible. (For instance report the length of the string going in and coming out. If they differ, you know what it is.)

If neither of those two naive guesses helps, you really need to create a minimal test case. Do you have a reliable interaction that does it? Can you script that interaction on the command line? Once you get to that point, try to start cutting out steps, and keep on going until you have the shortest case you can that reproduces it. After you get there, you are going to be in a much better position to figure out what it is.

Replies are listed 'Best First'.
Re: Re (tilly) 1: FreezeThaw Problem
by blackjudas (Pilgrim) on Aug 23, 2001 at 21:26 UTC
    My apologies for being vague, while I cannot seem to reproduce it on the command line, I will go ahead and write a different script with the same logic. In answer to your suggestions, the field that FreezeThaw freezes data to is set to MEDIUMTEXT which means that the theoretical limit is 16777215 characters which in testing I don't come close to. What I believe the problem to be (just venturing a guess) is that the version of Mozilla I'm testing this with may be broken since I cannot reproduce the error on the command line and it never errors with MSIE. Well thanks for the reply I just ended up throwing in a couple of filters to strip then add spaces. Seems to have cleared the problem up just fine. Man now if I could only write clearer posts eh? Grazias for the input.