Re: Microfocus & Oracle data types
From: Michael Russell (michael.russell_at_spamex.dsl.pipex.com)
Date: 08/12/04
- Next message: Chuck Stevens: "Re: Conversion Problem"
- Previous message: Michael Russell: "Re: Microfocus & Oracle data types"
- In reply to: Robert Jones: "Re: Microfocus & Oracle data types"
- Next in thread: docdwarf_at_panix.com: "Re: Microfocus & Oracle data types"
- Reply: docdwarf_at_panix.com: "Re: Microfocus & Oracle data types"
- Reply: James J. Gavan: "Re: Microfocus & Oracle data types"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 12 Aug 2004 17:01:10 +0100
Top posting:
Thanks, Robert.
SQL is fairly new to me ... and it seems to be getting 'newer' the more I
practice!
(I'm yet to cross the pons assinorum - which, for RDBMSes, I define as a
3-table join that works the way I intend :-))
I'm about to read up on Coalesce now ... think I'd better also user null
indicators, as well, though.
Thanks & Regards
Michael
"Robert Jones" <rjones0@hotmail.com> wrote in message
news:6dd8322.0408111103.7a580e23@posting.google.com...
> Top posting
>
> Hello Michael
>
> While the others have solved your immediate problem, you might
> consider using the COALESCE function another time, it can be easier to
> apply than using indicator variables for data retrieval. COALESCE is
> a relative latecomer to SQL, in DB2 it was previously called VALUE,
> Oracle might have another name for it. It is used as follows (from
> rusty memory):
>
> COALESCE(column-name,default-value-for-nulls), where the first
> non-null value in the parameter list of the function is used as the
> value to be retrieved in a SELECT.
>
> Regards, Robert
>
> "Michael Russell" <michael.russell@spamex.dsl.pipex.com> wrote in message
news:<4118f3dd$0$20249$cc9e4d1f@news-text.dial.pipex.com>...
> > Well, thanks for the input, the two gentlemen ... & please excuse the
> > top-posting ...
> >
> > I've added null-indicators to all appropriate parts of the 'fetch' - and
> > it's all OK now.
> >
> > Oddly, when using Sybase, there was a SQLWARN that they were missing (I
> > think, even when no null had been returned, but please correct that if
needs
> > be), but not in this scenario.
> >
> > Nice what comes into your mind as you walk home from work, relatively
> > carefree, sometimes.
> >
> > The finished work would have had them - but when you're (I'm) building
an
> > application, trialing the important parts comes before coding the whole
lot.
> >
> > Thanks again
> >
> > Michael
> > "Michael Russell" <michael.russell@spamex.dsl.pipex.com> wrote in
message
> > news:4117e2e2$0$20253$cc9e4d1f@news-text.dial.pipex.com...
> > > Greetings,
> > >
> > > I'm having trouble with ESQL:
> > >
> > > Scenario:
> > > Oracle 9i running on my PC (seemed a good idea)
> > > Microfocus Cobol 3.014 ditto
> > > I'm not using a pre-compiler.
> > >
> > > When using a cursor to fetch an Oracle-defined Decimal(7,3), no
data-type
> > > I've tried as the receiving variable seems to work.
> > > I've tried: MF's ESQL tool-generated s9(4)v9(3) Comp-3 and my own
> > > interventions with plain Comp & then plain Display.
> > >
> > > My 'evidence' is from inspecting via the Animator. Also, moving the
> > variable
> > > to another, 9(4)v999 display & inspecting that.
> > >
> > > Any hints would be welcome. .... (no such apparent trouble using
Sybase
> > > <sigh>)
> > >
> > > Regards
> > >
> > > Michael
> > >
> > >
- Next message: Chuck Stevens: "Re: Conversion Problem"
- Previous message: Michael Russell: "Re: Microfocus & Oracle data types"
- In reply to: Robert Jones: "Re: Microfocus & Oracle data types"
- Next in thread: docdwarf_at_panix.com: "Re: Microfocus & Oracle data types"
- Reply: docdwarf_at_panix.com: "Re: Microfocus & Oracle data types"
- Reply: James J. Gavan: "Re: Microfocus & Oracle data types"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|