Re: Problems making equivalent of a 'Memo' field. - Cris Perdue - com.mysql.lists.java

4 messages in com.mysql.lists.javaRe: Problems making equivalent of a '...

From	Sent On	Attachments
Instant Installer Support	19 Jan 2000 03:43
Cris Perdue	19 Jan 2000 08:16
LEBLANC, CLAUDE	19 Jan 2000 13:51
Instant Installer Support	19 Jan 2000 20:41

Subject:	Re: Problems making equivalent of a 'Memo' field.
From:	Cris Perdue (cr...@perdues.com)
Date:	01/19/2000 08:16:11 AM
List:	com.mysql.lists.java

The problem is that the MSAccess database table has "Memo" field i.e. unlimited characters. We thought that the "Long TEXT" type field in mySQL will serve as equilvalent to the 'Memo' field...is that right??...our main concern is the unlimited string property in 'Memo field'.

But when we tried with 'Long TEXT' or 'LONG BLOB' we get the following error in our browser....

E0401 error in API method getIndexInfo() E2300 Error in DBMDtable() constructor E2200 Error in DBMDtableColumn constructor

Now, the error is removed, if we replace that field with 'MEDIUM TEXT' or 'MEDIUM BLOB'. But that does not seem to have unlimited capacity.

Looks like a bug somewhere in somebody's handling of LONG TEXT. But for the moment you might as well move ahead with MEDIUM TEXT. A MEDIUM TEXT field will hold enough data to fill several large books with text; it's already pretty unlimited.