That is not a bad idea after all, can't remember who suggested it
(probably Connor McDonald), but, for example, I have few procedures
that generates "generic" code for lookup/update functions (static
sql) for a given table. Later, I insert this generated code into a
package and modify it if I have to. I think this idea (and many many
others) is also implemented in qnxo by Steven Feuerstein.
On 8/23/05, rjamya <rjamya_at_gmail.com> wrote:
> probably some OO developers thought of this.
>
> I recently saw one of the _funniest_ idea cooked up by (supposedly) OO
> developer for a _generic_ lookup query. It has been 4 days since I shot it
> down, but it still cracks me up.
>
> Raj
>
> On 8/23/05, David Sharples <davidsharples_at_gmail.com> wrote:
> > Depends if you take the OP's questions literally. If you want to use
> > a proc to find out the sequence's nextval then you need to do it that
> > way.
> >
> > You could just select in form dual normally without doing a proc - all
> > depends on what the OP actually wants
> >
> >
> > On 8/23/05, Ram K <lambu999_at_gmail.com> wrote:
> >
> > > Cant we select directly from a sequence without having to use a
> > > function? Is there any advantage to using a function?
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
>
>
>
> --
> ------------------------------
> select standard_disclaimer from company_requirements where category =
> 'MANDATORY';
>
--
Best regards,
Edgar Chupit
callto://edgar.chupit
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Aug 26 2005 - 13:51:59 CDT
