RE: LOB Operation and SQL*Net Message From Client and cursor #0
From: Larry Elkins <elkinsl_at_verizon.net>
Date: Wed, 01 May 2013 19:27:57 -0500
Message-id: <005101ce46cb$e4f80d10$aee82730$_at_net>
Maybe there for future uses, or maybe a specific configuration for our environment limiting it to 255 and other clients of theirs use more than 255. Regardless, I can see where someone could make the decision to use an NCLOB for something like "comments" so more than 4000 characters could be used. Just don't know the reason behind it being there right now. I'm sure they have a good reason ;-)
Date: Wed, 01 May 2013 19:27:57 -0500
Message-id: <005101ce46cb$e4f80d10$aee82730$_at_net>
Maybe there for future uses, or maybe a specific configuration for our environment limiting it to 255 and other clients of theirs use more than 255. Regardless, I can see where someone could make the decision to use an NCLOB for something like "comments" so more than 4000 characters could be used. Just don't know the reason behind it being there right now. I'm sure they have a good reason ;-)
Larry G. Elkins
elkinsl_at_verizon.net
Cell: 214.695.8605
> -----Original Message-----
> From: Yong Huang [mailto:yong321_at_yahoo.com]
> Subject: RE: LOB Operation and SQL*Net Message From Client and cursor #0
> > the front end limits the [LOB comments] field to 255 characters
>
> That's even worse in the design.
>
> Yong Huang
-- http://www.freelists.org/webpage/oracle-lReceived on Thu May 02 2013 - 02:27:57 CEST