Re: lvarchar and IUS...

In article <1998May25.164236@informatik.uni-kl.de>, Marcus Flehmig - Hiwi Nink <flehmig@informatik.uni-kl.de> wrote: >In article <6kbt5l$8f3$1@server-b.cs.interbusiness.it>, "Tr@sh" ><trebian@newtech.it> writes: >|> A little problem... I have a table with an lvarchar (32k) column. When I >|> insert some data into this this column (in dbaccess, from a form o from a >|> file) is all right. When i try to retrive this column, the data is truncate >|> at 2kbytes about. Somebody have the same problem? >|> >|> I work on IUS 9.13 with Sinix S.O. > >Yes me, but imho it's correct! >See: >http://www.informix.com/answers/oldsite/answers/pubs/html/dbdk/faq/faq.fm.html#997164 > ><cite on> >F:What is the maximum size of the LVARCHAR data type? > >Q:When an LVARCHAR data type is stored in a database table, >it has a maximum size of 2KB. Attempts to insert more than 2KB >of text into a table are silently truncated to 2KB. >LVARCHAR is also used to pass data to DataBlade routines. >In this context, there is no limit to the size of the LVARCHAR. ><cite off> > Actually the answer is a bit more complex than that... The limit for lvarchar is actually 32K right now. Part of the limit comes from the SQL/I transport layer that uses a 16-byte length field. In a previous version a bug that kept the transport size to 2K was fixed for server-to-client transfers. It was not however fixed for the other direction until recently. I the server team here at Informix is working on a more generic set of fixes to change the 16-bit fields (which occur all over the place). This should open up the maximum row size and multi-represenational data automatically. While the transport layer has been fixed there are still issues hardcoded into some of the client components. I believe that esql/c still has the 2K limit in some situations. The problem disappears on simple insertions in esql/c but shows up when using insert cursors. Since both dbaccess and dbload both use insert cursors for performance reasons they were the prime cause of 2K limit problems. I have been told that this bug has been fixed for a while. =============================================================================== Albert Landeck | We are quite confident that all of our servers Informix Software | and DataBlades are Year 2000 Compliant. However, landeck@informix.com | we have over a two year backlog of Year 2000 Video DataBlade | Compliance forms to fill out, so according to our and | scheduling database, you should hear back from Client Visualization | us in June, 1900.