SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-19-2008, 06:38 PM
| ||||
| ||||
 VARCHAR or not ? 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      |
|
04-19-2008, 06:38 PM
| |||
| |||
| Re: VARCHAR or not ? .... > 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 |
|
04-19-2008, 06:39 PM
| |||
| |||
| Re: VARCHAR or not ? 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. |
|
04-19-2008, 06:39 PM
| ||||
| ||||
| Re: VARCHAR or not ? 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 |
 |
« Re: If You have an option to move from 7.3 to 9.3 or 9.4. Which one you prefer 9.3 or 9.4
|
Re: Querix Debug »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 09:37 AM.
