On Tue, 04 Nov 2003 21:18:34 -0500, KalpanaPai wrote:
> Hi All,
>
> We are using informix 9.21 on solaris.
>
> In a table we have a column of type lvarchar which is called defaultvalue, as
> it can store 2048 chars, the client has supplied the data which is more than
> 2048 chars.
>
> We need to find an alternative datatype to store more than 2048.
>
> Is it better to use 2 or 3 columns for the the same value as 1.defaultval1
> lvarchar, defaultval2 lvarchar .... or
> 2. to use CHAR (3000) or more
> 3. Split the column into more than 1 col as VARCAHR(255) (In this case what
> happens to the existing data?)
How about:
4. Push the column down to a child table with just the primary key/serial
columns of the original table, a sequence number (smallint or int), and the
CHAR/VARCHAR/LVARCHAR
This way you can support unlimited text, because no matter what the analysts and
users tell you one day the text storage requirement for this object may even
outgrow an IDS v9.4 VARCHAR's capacity at 32K. This is a much more flexible
schema and is normalized while multiple columns that have to be concatenated to
form a logical column is not.
Art S. Kagel
> Can anybody suggest me which is more feasible to use in this type of
> requirement, if we use CHAR /LVARCHAR will it slow down the search and
> select's ?
> As we have to fix this pblm for the client. Any suggestions highly
> appreciated.
>
>
> Thanks in Advance
> Kalpana Pai