<ctcgag_at_hotmail.com> wrote in message
news:20031004150540.469$nr_at_newsreader.com...
> "Jim Kennedy" <kennedy-down_with_spammers_at_no-spam.comcast.net> wrote:
> > "Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message
> > news:1a75df45.0310020430.6339ced4_at_posting.google.com...
> > > Hans Forbrich <forbrich_at_yahoo.net> wrote
> > >
> > > > The only possible argument against such religious drivel might be
> > Chapter
> > > > 1 of Kyte's expert one-on-one.
> > >
> > > Good, call. I've just photostated the first few pages and will be
> > > handing it out at the next architecture meeting.
> > >
> > > > But it's an uphill battle precisely because it's religious (pure
> > > > belief without, or deliberately ignoring, any visible means of
> > > > support).
> > >
> > > Exactly. Which is why I'm trolling for comments and opinions, backed
> > > up personal experience, to also present at the next meeting.
> > >
> > > One of the problems I face is the perception that I'm an Oracle
> > > fanatic saying that as much as possible must be done in the database.
> > > It's difficult to change this perception and show that it is a common
> > > and the best practise method - and nothing to do with Oracle
> > > "fanatacism".
> > >
> > > So, how do you counter the opinion that Oracle should be a bit bucket
> > > without sounding like a fanatic?
> > >
> > > --
> > > Billy
> >
> > Billy,
> > Ouch! Hard to deal with people who are unreasonable. Years ago I
worked
> > at a company that used a CRM from a company called Onyx. I don't know
if
> > it is different now, but at that time Onyx only ran on SQLServer. The
> > architecture of the application was that ALL business rules etc. were in
> > the database. They called stored procedures for everything. The
> > internet boom, everything must be a thin client craze came along. They
> > fairly quickly turned their CRM into a web based company CRM portal.
Gee
> > how did they do that? They didn't have to change the back end, just the
> > GUI (web server stuff instead of a Visual Basic client server
> > application.
>
> So now postulate that instead of calling stored procedures for everything,
> they called DAO methods for everything. How does this make things
> different with respect to the web-based change?
>
> Xho
>
> --
> -------------------- http://NewsReader.Com/ --------------------
> Usenet Newsgroup Service New Rate! $9.95/Month 50GB
DAO methods don't exist in Java or Fortran, PHP, CGI,PERL, etc. (whatever
the hot language of the moment is) They spent a lot less time recoding the
business logic (none). They did spend time recoding the GUI logic, but one
would expect to since they were changing the GUI. (not the business logic)
As a matter of fact they could use both GUIs at the same time and not have
to recode the stored procs.
I don't think you get it.
Jim
Received on Sat Oct 04 2003 - 14:24:42 CDT
