VARCHAR or not ?
Dirk Moolman needed a lookup table with a description of up to 2000 characters on IDS 7.31 FD3, where VARCHAR is limited to 255. Gorazd Hribar Rajteric said CHAR(2000) is needed (TEXT possible but not advised) or split lines. Obnoxio The Clown suggested upgrading to 9.30/9.40 for a larger LVARCHAR. Art Kagel advised a child table with key, sequence number and small VARCHAR lines.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Solaris 8 IDS 7.31 FD3 We have to create a table, that will contain a code, a short description and then a long description (up to 2000 characters). This is basically a lookup table, and will be used for browsing, verifying and selecting codes. Varchar has a limit of 255 characters. Does this mean I have to define a char(2000) column for the long description ? Any suggestions ? Regards Dirk sending to informix-list
... > Varchar has a limit of 255 characters. Does this mean I have to define a char(2000) column for the long description ? Basically - YES. You could also use TEXT field, but I wouldn't recommend it. > Any suggestions ? Split your description into multiple lines which can then be of VARCHAR type. Gorazd
Dirk Moolman wrote: > Solaris 8 > IDS 7.31 FD3 > > > We have to create a table, that will contain a code, a short description > and then a long description (up to 2000 characters). This is basically a > lookup table, and will be used for browsing, verifying and selecting > codes. > > Varchar has a limit of 255 characters. Does this mean I have to define a > char(2000) column for the long description ? > > Any suggestions ? Upgrade to 9.30 or 9.40 -- use the LVARCHAR data type, which can now be (I think) up to 32K. Definitely 2K.
On Tue, 09 Sep 2003 06:07:50 -0400, Dirk Moolman wrote: Split the description in to a subsidiary table containing just the key, a sequence number, and a small CHAR or VARCHAR (say 80 or 100 bytes per record). If the natural key of the parent table is too long add a SERIAL column in the parent table and use that as the key to the child table along with the sequence number. Then you can have as many or as few detail lines as needed with minimal waste. Art S. Kagel > Solaris 8 > IDS 7.31 FD3 > > > We have to create a table, that will contain a code, a short description and > then a long description (up to 2000 characters). This is basically a lookup > table, and will be used for browsing, verifying and selecting codes. > > Varchar has a limit of 255 characters. Does this mean I have to define a > char(2000) column for the long description ? > > Any suggestions ? > > > Regards > Dirk > > > > sending to informix-list