RE: [Zope] LONG insert > 2000 chars fail
Use ? > -Original Message- > From: Andy Gates [mailto:[EMAIL PROTECTED]] > Sent: Thursday, July 06, 2000 10:32 AM > To: [EMAIL PROTECTED] > Subject: Re: [Zope] LONG insert > 2000 chars fail > > > Message-ID: <[EMAIL PROTECTED]> > Priority: NORMAL > X-Mailer: Execmail for Win32 5.1 Build (9) > MIME-Version: 1.0 > Content-Type: Text/Plain; charset="us-ascii" > > Possibly related: Webform-based news story editor generates > long text > strings for body text. Using an ordinary form, this ends up > (url-encoded) in the URL, but it's betting truncated after about 2000 > chars. Many of my stories are longer than that. What to do? > > AndyG > > ___ > Zope maillist - [EMAIL PROTECTED] > http://lists.zope.org/mailman/listinfo/zope > ** No cross posts or HTML encoding! ** > (Related lists - > http://lists.zope.org/mailman/listinfo/zope-announce > http://lists.zope.org/mailman/listinfo/zope-dev ) > ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] LONG insert > 2000 chars fail
Message-ID: <[EMAIL PROTECTED]> Priority: NORMAL X-Mailer: Execmail for Win32 5.1 Build (9) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Possibly related: Webform-based news story editor generates long text strings for body text. Using an ordinary form, this ends up (url-encoded) in the URL, but it's betting truncated after about 2000 chars. Many of my stories are longer than that. What to do? AndyG ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] LONG insert > 2000 chars fail
On Thu, Jul 06, 2000 at 08:48:43AM -0400, Satheesh Babu wrote: > Hi, > > We use Oracle v 8.1.5 and 8.1.6 and there we can go upto > 5000 characters for string literals. Anyway, LONG is a > deprecated datatype and we decided to use detail tables > for text more than 4000 chars. Any given string will be > split at 4000 chars and inserted as one or more records > into detail table, as varchar2 fields. Varchar2 fields > are easy to process also. Yes, you are right, we are using 8.1.5 On Linux, and it swallows up to 4k. But having to split a string to get it in the database feels pretty stupid. > I think it is more of an Oracle OCI problem than OracleDA. Yep, I tried to look at oci.c/oci.i sources and got shocked... Maybe overnight I'll gather some courage to see if it would be feasible to use 'bind variables' to push data in to the long columns. Or will it be easier to split text with a python external method. -- Riku Voipio [EMAIL PROTECTED] 09-862 60764 ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )