RE: IDS2000 disallows nulls into INT fields of Stored Procs?
Posted in 2000
Topics: Stored Procedures & SPL, Server Administration
Sorry for being so late in responding to you.
We're working with Informix Dynamic Server 2000 Version 9.20.UC3
So, I suppose the problem was fixed in UC4.
Thank you for your response,
Michel
> -----Original Message-----
> From: Watson, Paul [SMTP:Paul.Watson@aggregate.com]
> Sent: Wednesday, November 08, 2000 4:31 AM
> To: 'Michel Rheaume'; informix-list@iiug.org
> Subject: RE: IDS2000 disallows nulls into INT fields of Stored Procs?
>
> What version? We are using 9.20.UC4 and don't see this
>
> Paul Watson #
> WF Software Ltd # All answers are
> +44 1435 674629 # pure fantasy
> +44 1436 678693 #
> www.wfsoftware.com/informix #
>
>
> > -----Original Message-----
> > From: Michel Rheaume [mailto:michel.rheaume@tecsys.com]
> > Sent: Tuesday, November 07, 2000 04:50
> > To: informix-list@iiug.org
> > Subject: IDS2000 disallows nulls into INT fields of Stored Procs?
> >
> >
> > Hi,
> >
> > We're converting to IDS2000 and we receive the following error when
> > calling a stored procedure with a null value in an Integer
> > input parameter
> > field:
> > Value exceeds limit of INTEGER precision
> >
> > This proc worked well in Informix 7.3. The field was
> > defined as NULLS =
> > Yes to allow Nulls. This value was updated into the database
> > later into the
> > stored proc. But, it's failing coming in.
> >
> > If we do dbaccess we ARE still allowed to do an update of
> > a value stated
> > as NULL or "", so it's not failing at the update.
> >
> > If anyone has experienced this and found a solution other
> > than changing
> > the stored proc I'd appreciate your comments. Maybe there's
> > a database
> > parameter which would avoid us having the massage the data
> > coming into the
> > stored procedure??
> >
> > Thank you,
> >
> > Michel
> >
> >