Re: bind param problem

2001-02-07 Thread Rajesh Yenumulapally
The original oracle error message was ORA-01400: cannot insert NULL into ("GRCT"."CGNT222_HELP_USER"."ID_RACF") (DBD ERROR: OCIStmtExecute) instead of ORA-01008: not all variables bound (DBD ERROR: OCIStmtExecute). (apologize for the miscommunication) --- Rajesh Yenumulapally <[EMAIL PR

Re: bind param problem

2001-02-07 Thread non-HP
> "Michael" == Michael Peppler <[EMAIL PROTECTED]> writes: Michael> There was a fairly long thread in comp.databases.sybase on Michael> this issue. Joe Celko weighed in with this comment: Found it. http://www.deja.com/[ST_rn=ps]/threadmsg_ct.xp?AN=714120405&fmt=text Michael> 4) Attempti

Re: bind param problem

2001-02-07 Thread Rajesh Yenumulapally
Hi again here I am using the same databse for both the web servers.I am getting the error ORA-01008: not all variables bound (DBD ERROR: OCIStmtExecute). Based on this shall I am assume there is something fault with the installation and configuration of the DBI or DBD::Oracle on the web server rat

Re: bind param problem

2001-02-07 Thread Michael Peppler
Tony Foiani writes: > > "Michael" == Michael Peppler <[EMAIL PROTECTED]> writes: > > Michael> I believe that SQL-92 mandates that a non-null string be at > Michael> least one character in length. > > Interesting. The Oracle docs say: > Michael> Certainly Sybase (and I presume MS-S

Re: bind param problem

2001-02-07 Thread Tony Foiani
> "Michael" == Michael Peppler <[EMAIL PROTECTED]> writes: Michael> I believe that SQL-92 mandates that a non-null string be at Michael> least one character in length. Interesting. The Oracle docs say: Oracle currently treats a character value with a length of zero as null. However,

Re: bind param problem

2001-02-07 Thread Stephen Clouse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 07, 2001 at 09:50:23AM +0100, Hans-J. Krause wrote: > A database *never* should accept an insert of an empty string in a not null > column Actually, it should. According to SQL-92, '' != NULL. Oracle has threatened to fix the behavior f

Re: bind param problem

2001-02-07 Thread Michael Peppler
Tony Foiani writes: > > "Hans-J" == Hans-J Krause <[EMAIL PROTECTED]> writes: > > Hans-J> A database *never* should accept an insert of an empty string > Hans-J> in a not null column - otherwise what for should a > Hans-J> not-null-check to be set? > > If you said "Oracle database",

Re: bind param problem

2001-02-07 Thread Tony Foiani
> "Hans-J" == Hans-J Krause <[EMAIL PROTECTED]> writes: Hans-J> A database *never* should accept an insert of an empty string Hans-J> in a not null column - otherwise what for should a Hans-J> not-null-check to be set? If you said "Oracle database", I'd agree. (And, given the rest of your

Re: bind param problem

2001-02-07 Thread Hans-J. Krause
A database *never* should accept an insert of an empty string in a not null column - otherwise what for should a not-null-check to be set? On the otherhand your string is not empty (1 blank: ' '), but in standard oracle is making an ltrim() on strings before inserting to remove leading blanks -

Re: bind param problem

2001-02-06 Thread Rajesh Yenumulapally
F.Y.I The real error I am getting is the Oracle table does not accept null values, because all the columns are not null.And I guess that shouldn't matter since I am sending an empty string. The same script works on most of my other servers(inserting an empty string in a not null column) exce

Re: bind param problem

2001-02-06 Thread Stephen Clouse
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Feb 06, 2001 at 11:53:04AM -0800, Rajesh Yenumulapally wrote: > Hi > I wrote a script which uses a bind_param function of the DBI and it works > perfectly fine on one server but not on the other one. My first server has the > perl 5.003/DBI 0