Re: Oracle vs. MS-SQL dialects

You are basically going from transact sql to pl/sql which is Pascalish. In triggers you do have the before and after values and don't have to select them out of the table you just changed.
In general in Oracle you should use packages to group related functions and procedures togther.
You would use ref cursors for returned result sets, and sequences for autonumber.

If it were me I would try to group the procedures logically and then start rewriting them one group at a time.

Jim

"Jon Waterhouse" <jonwaterhouse_at_mail.gov.nf.ca> wrote in message news:3c0e6349.0_at_209.128.1.3...
> 8.1.6, because I had to host it on a Netware server.
>
> Jim Kennedy <kennedy-family_at_attbi.com> wrote in message
> news:JWrP7.1337$802.116725_at_rwcrnsc53...
> > What version of Oracle? I believe 9i supports the inner and outer join
> > syntax.
> > Jim
> >
> > "Jon Waterhouse" <jonwaterhouse_at_mail.gov.nf.ca> wrote in message
> > news:3c0e423c.0_at_209.128.1.3...
> > > I have about 900 lines of stored procedure code that I wrote in MS-SQL
> > that
> > > I need to transfer to run on an Oracle database.
> > >
> > > I know there are some things I have to change, in particular:
> > >
> > > parameter passing, which have to be explicitly passed as in out or in
> out
> > >
> > > all my SELECT ... FROM sometab INNER JOIN someothertab ON
> > > somefield=someotherfield WHERE ...
> > > will have to have the JOIN info put into the WHERE clause using +
> > operators
> > > for outer joins etc.
> > >
> > > What would replace
> > >
> > > DECLARE @val
> > > SET @val=1
> > > select * from tab where sexval=@val
> > >
> > > would it be
> > >
> > > DEFINE val=1
> > > select * from tab where sexval=&val
> > > UNDEFINE val
> > >
> > > or am I missing something?
> > >
> > > Thanks,
> > >
> > > Jon
> > >
> > >
> >
> >
>
>
Received on Wed Dec 05 2001 - 12:50:25 CST