Fix the undefined variable warnings and put -w back. It will save you a lot of grief in both the short and long run. If I even slightly suspect I might be doing the same thing more than once, both 'use strict and '-w' are part of the boilerplate. If the task was worth enough effort to create a file, they probably belong in there.
The original error you reported was a complaint that you were using SQL_LONGVARCHAR in the bind_param() call for a column that wasn't LONG. Please correspond through the email list. I am not the sole source of wisdom. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "Morrison Davis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, January 27, 2002 15:13 Subject: Re: What am I missing? with this bind stuff > Got it working, your right about the -w switch a and USE Strict. > I wasn't using I don't use -w switch because I always get the using > uninitialized variable errors. I did move the date and nextval statements > to the prepare line and removed the question marks for those columns but > I think I ran into some oracle bug because while testing I still got the > LONG error if my REPLY variable contained 4000 characters but it would > work if there were 3999. Oracle must automatically consider it to be a long > anything over 3999.
