Re: pl./sql deployment stragegies?

"Marc Blum" <blum_at_marcblum.de> wrote in message news:o1iol0dfhl31toq3ebdsop67763n9ghveo_at_4ax.com...
| On Thu, 30 Sep 2004 09:47:24 -0400, "Mark C. Stock" <mcstockX_at_Xenquery
.com>
| wrote:
| >are any of you aware of any VCS products that manage check-in check-out
at
| >the database level so that once checked out, nobody can overwrite the
object
| >unless connected and verified as the developer that checked it out? i.e.,
| >true clobber-protection enforced at the database level, not just at the
tool
| >level?
|
| If any developer has checked out the source code of any database object,
edited
| it and put in into the database, how come, that another developer has the
same
| source code and changes the object?
|
| You seem to have serious flaws in your development process.
|
| 1) version control rules! you gotta have one and only one place to manage
the
| current version of any object. There are plenty of tools on the market
providing
| this.
|

...

you seem to have a great deal of special knowledge about my development process ;-)

the point is, a VCS product that relies on everyone using the same tool rather than on database security (as apparently TOAD Team Programming does) leaves back doors open

can you provide some constructive information about which of the 'plenty of tools on the market' (which hopefully you know even better than you know my development process) provides control integrated to the database, rather than outside the database?

++ mcs Received on Thu Sep 30 2004 - 13:40:01 CDT