Re: [ADVANCED-DOTNET] OT Continous Integration

2004-05-04 Thread Darrel Miller
TECTED] > Subject: Re: [ADVANCED-DOTNET] OT Continous Integration > > I have to say I agree with the comments so far and to add I > have used ORM since "InfoModeler Q" and have all Terry's > books on the subject. > > In a new db design I would always start with

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-22 Thread Sathiamurthy, Venkat
My 2 cents: cut out the Nke syndrome. -Original Message- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Sami Vaaraniemi Sent: Thursday, April 22, 2004 2:26 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] OT Continous Integration On

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Sami Vaaraniemi
On Wed, 21 Apr 2004 16:36:51 -0400, Gary Davidson <[EMAIL PROTECTED]> wrote: >The db is a different story. A developer opens enterprise mgr and makes a >quick change and then "forgets" to notify anyone of the change script. We >don't find out until the build or someone happens to do a get latest a

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Gary Davidson
evelopment builds and find the integration errors sooner. Maybe "That dog just won't hunt". Gary Davidson From: Frans Bouma <[EMAIL PROTECTED]> Reply-To: "Unmoderated discussion of advanced .NET topics." <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Tiseo, Paul
vanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Frans Bouma > Sent: Wednesday, April 21, 2004 4:01 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] OT Continous Integration > > > I'll add to my own post that the conceptual/ORM approach i

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Frans Bouma
f > Tiseo, Paul > > Sent: Wednesday, April 21, 2004 2:55 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [ADVANCED-DOTNET] OT Continous Integration > > > > Curious, are you using CruiseControl or Draco? > > > > To some degree, Frans is right. Controlling t

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Tiseo, Paul
cussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Tiseo, Paul > Sent: Wednesday, April 21, 2004 2:55 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] OT Continous Integration > > Curious, are you using CruiseControl or Draco? > > To some deg

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Tiseo, Paul
From: Unmoderated discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Gary Davidson > Sent: Wednesday, April 21, 2004 10:54 AM > To: [EMAIL PROTECTED] > Subject: [ADVANCED-DOTNET] OT Continous Integration > > Are there any Continous Integration shops

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread J. Merrill
In some work I've done for a client (SQL Server backend, not using .NET), there are three different mechanisms to handle this. They all share a concept -- there is an in-memory representation of the database schema. The details of the representation are different. There are routines that, giv

Re: [ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Frans Bouma
Forget Agile development for database models, as it results in ad-hoc changes to a relational model which should be generated from an abstract model in the first place. This means that if you set up your relational model by generating it from an ORM/NIAM model (http://www.orm.net) for example by

[ADVANCED-DOTNET] OT Continous Integration

2004-04-21 Thread Gary Davidson
Are there any Continous Integration shops on the list? How do you handle database changes? I am working toward having my team use continous integration as part of our move to AGILE programming methodologies. The one problem I can't seem to solve (i.e make everyone happy) is changes to the database.