From: Gogala, Mladen [SMTP:[EMAIL PROTECTED]]
> Sent: Tue, January 15, 2002 6:40 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Using procedures instead of coding update/insert
> SQL...huh?
>
> How about being an intuitive DBA. Sort of zen Buddhism and the
> da
Good, I did not use Steve's name in vain.
-Original Message-
Carmichael
Sent: Tuesday, January 15, 2002 8:27 AM
To: Multiple recipients of list ORACLE-L
we did it on a non-java project. Steven developed a product, PL/Vision,
which helps you to do this.
anything that doesn't clog my sha
you oughta apologize to Robert Pirsig, the guy who started the whole thing.
-Original Message-
Sent: Tuesday, January 15, 2002 12:35 PM
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED] wrote:
>oh, now I owe you a royalty for naming a new book "Zen and the Art of
>Database Ad
January 15, 2002 6:40 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Using procedures instead of coding update/insert
> SQL...huh?
>
> How about being an intuitive DBA. Sort of zen Buddhism and the
> database administration? Can you feel the pain of your oracle
[EMAIL PROTECTED] wrote:
>oh, now I owe you a royalty for naming a new book "Zen and the Art of
>Database Administration" (my apologies to the author of Zen and the Art
>of Archery)
>
somehow i don't think he'll mind.;-)
--
--
Bill "Shrek" Thater ORACLE DBA
[EMAIL
r daily life).
> >
> > Yechiel Adar, Mehish Computer Services
> > [EMAIL PROTECTED]
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > > Sent: Tue, January 15, 2002 3:25 PM
> > > To: Mu
PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > Sent: Tue, January 15, 2002 3:25 PM
> > To: Multiple recipients of list ORACLE-L
> > Subject:Re: Using procedures instead of coding update/insert
> > SQL...huh?
> >
> > I've seen this done also on
we did it on a non-java project. Steven developed a product, PL/Vision,
which helps you to do this.
anything that doesn't clog my shared pool is a good thing :)
--- Kimberly Smith <[EMAIL PROTECTED]> wrote:
> I heard of it done on non-java projects. Steve Feuerstein (O'Reilly
> author)
> is/was
m that use
> them.
> In short 'MAINTENANCE' (which is 70-80% of our daily life).
>
> Yechiel Adar, Mehish Computer Services
> [EMAIL PROTECTED]
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > Sent: Tue
I heard of it done on non-java projects. Steve Feuerstein (O'Reilly author)
is/was pretty big on it if I remember. What is does is provide consistent
access to your SQL. When you consider the way the cost based optimizer
works
and the fact that the slightest difference in spacing or whatever in
nuary 15, 2002 3:25 PM
> > To: Multiple recipients of list ORACLE-L
> > Subject:Re: Using procedures instead of coding update/insert
> > SQL...huh?
> >
> > I've seen this done also on a Java project. My understandi
; [EMAIL PROTECTED]
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> > Sent: Tue, January 15, 2002 3:25 PM
> > To: Multiple recipients of list ORACLE-L
> > Subject:Re: Using procedures instead of coding update/inser
our daily life).
Yechiel Adar, Mehish Computer Services
[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Tue, January 15, 2002 3:25 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Using procedures instea
; Subject: Re: Using procedures instead of coding update/insert
> SQL...huh?
>
> I've seen this done also on a Java project. My understanding was that it
> had to do more with the way an object oriented programmer's mind worked
> than with any code efficien
[EMAIL PROTECTED]]
> Sent: Tue, January 15, 2002 3:25 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Using procedures instead of coding update/insert
> SQL...huh?
>
> I've seen this done also on a Java project. My understanding was that it
> had
I've seen this done also on a Java project. My understanding was that it
had to do more with the way an object oriented programmer's mind worked
than with any code efficiency.
"Grab
DITTO THAT!!!
You can also use PL/SQL for selects, not just inserts, updates and deletes.
You do this by having the PL/SQL return a reference cursor and then the Java
code takes it from there to display everything via jsp or whatever. I was
DBA where we did this on a Java/Oracle development proje
It makes absolute sense to use this encapsulated approach, because you don't
have to keep changing your code for DML every time table structure changes,
plus this way you guarantee that everyone will use the same statement
promoting its reuse in the SGA.
Oracle designer likes to call this approac
Chris,
I personally think this is the best approach. Think of the application
task:
1). Is it easier to perform Database Processing within PL/SQL than within
Java? PL/SQL is a very strong development tool. Code development and
maintenance-wise, I think it is much easier to do all the work i
We used it at a former site. The idea is, this makes the JAVA code
totally reusable if you end up changing database servers. All you would
have to do is change the underlying insert and update procedures and
recompile the application code.
I can see a use for it even if you aren't changing databa
Chris:
Advantage:
1. More control over modifications to any table.
2. Better QA process as DBAs can ensure that all updates are performed
uniformly.
3. Less security involved as procedures act at the security of the owner,
except in 9i where security is also executed at the user level as we
21 matches
Mail list logo
