> Maybe I wasn't clear in my reply to that statement. There is
> nothing inherent about stored procedures which makes them
> better for separating out work. It is in fact the same amount
> of work to separate queries as it is stored procedures.
Well... As I already pointed out:
Developer1 - User Interface
Developer2 - ColdFusion Code
Developer3 - Queries/Procs
The separation of work here is beneficial since Developer 2 and 3 have to
share resources (CF files) and the project might not be architected in the
best way.
So Id say that it's better for separation of work. If I was Developer 3 and
had to constantly share a file(s) with developer 2, I think our progress
would be at a much slower pace.
Mike
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- Re: why are procedures better? (wa... Matt Liotta
- RE: why are procedures better? (was: RE: Securing CF App... Tangorre, Michael
- RE: why are procedures better? (was: RE: Securing CF App... Tangorre, Michael
- RE: why are procedures better? (was: RE: Securing CF App... Tangorre, Michael
- RE: why are procedures better? (was: RE: Securing CF App... Dave Watts
- RE: why are procedures better? (was: RE: Securing CF App... Stephen Barry
- Re: why are procedures better? (was: RE: Securing CF App... Tangorre, Michael
- Re: why are procedures better? (was: RE: Securing C... Matt Liotta
- RE: why are procedures better? (was: RE: Securi... Steve Nelson
- Re: why are procedures better? (was: RE: Se... Matt Liotta
- RE: why are procedures better? (was: RE: Securing CF App... Stephen Barry
- RE: why are procedures better? (was: RE: Securing CF App... Heald, Tim
- RE: why are procedures better? (was: RE: Securing CF App... Heald, Tim