He's not saying to never bother with DB portability, but instead he's saying that to look at your requirements, and to determine whether or not portability is required before automatically assuming it is.
Quote from the article:
"Of course, there is one exception to this. If you were to write an application that needed to be used with multiple DBMSs (commercial software, or applications distributed to other users) then portability is an obvious immediate concern."
----- Original Message -----
From: "Kazmierczak, Kevin" <[EMAIL PROTECTED]>
Date: Tuesday, March 23, 2004 9:39 am
Subject: RE: Securing CF Apps.
> I agree that Ben's article explains this very nicely. Not sure if
> thislink works or not:
>
> http://www.sys-con.com/coldfusion/article.cfm?id=705
>
> Kevin.
> _____
>
> From: Adrocknaphobia [EMAIL PROTECTED]
> Sent: Tuesday, March 23, 2004 11:36 AM
> To: CF-Talk
> Subject: Re: Securing CF Apps.
>
> the user/roles are in tables, they are just system tables.
>
> look, i dont want to get into the debate about coding for portability
> when it comes to dbs. you should def check out bens article on
> that one,
> as it was well written and he pretty much showed that there is so
> littlein common between databases that its pretty much impossible,
> and an
> incredible waste of time.
>
> -adam
> > -----Original Message-----
> > From: Tangorre, Michael [EMAIL PROTECTED]
> > Sent: Tuesday, March 23, 2004 04:28 PM
> > To: 'CF-Talk'
> > Subject: RE: Securing CF Apps.
> >
> >
> > > if you caught Ben's article in cfdj a month or two ago, he
> > > talks about how you shouldnt be too concerned with
> > > portability between databases. Afterall you'll be rewriting
> > > all your stored procedures anyway, so reliance on the user's
> > > table isn't the breaking point of portability.
> >
> > You may be rewriting your stored procedures but you may also find
> yourself
> > reworking your schema as well, not too mention the code that
> will be
> > affected. I can see having different user/passes for select, insert,
> update,
> > and delete ROLES but I prefer to keep my application roles and
> permissions
> > in tables. I guess to each his own method.. No one is right or
> wrong,just a
> > preference thing.
> >
> > > sides, how often does a shop really switch between SQL and Oracle?
> >
> > Not often but it happens.
> >
> > Mike
> >
> >
> _____
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
