>
>Aha, so 351 is "corrupted VarChar" !
According to the current documentation. 1.8.10 doc has no 351 error listed.
>Robert, again, clarify my questions in prev letter !
I just did.
>In 1.9.5 and 1.9.6 we have had no problems with VarChar.
VarChar have always been safe-heaven for me after all the troubles
with TEXT fields in earlier versions and I had NO problems whatsoever
with 1.8.10 until now.
>You better create FRESH db by LoadDump in 1.9.6.
>Do not use old db.
>
>And it must go away.
Going away is easy. The question is whether they come back under
1.9.6 as they do under 1.8.10. I really suspect that it is my program
or environment doing something to instigate this.
Robert
©2002 Robert Brenstein |
