+1 Rajesh. Its just that its difficult to enforce all. On 30/07/13 5:18 PM, "Rajesh Battala" <rajesh.batt...@citrix.com> wrote:
>That's a default solution. But the rate at which commits are making to >repo it's not easy to figure out which commits are causing db changes. >Hope you had already faced this situation > >Thanks >Rajesh Battala > > >> -----Original Message----- >> From: Koushik Das [mailto:koushik....@citrix.com] >> Sent: Tuesday, July 30, 2013 5:14 PM >> To: dev@cloudstack.apache.org >> Subject: RE: Request to inform which DB command to run on existing >>setup if >> any db schema changes >> >> Rajesh, >> You can look at the check-in history for schema-410to420.sql for the >>changes >> >> > -----Original Message----- >> > From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] >> > Sent: Tuesday, July 30, 2013 5:03 PM >> > To: dev@cloudstack.apache.org >> > Subject: Request to inform which DB command to run on existing setup >> > if any db schema changes >> > >> > Hi All, >> > Please share sql statements to be inserted in the dev list, if any db >> > schema changes are committed and require deploy db on existing setup . >> > This will save lots of development time. >> > More time is getting consumed in clearing the entire setup and set it >>again. >> > >> > Thanks >> > Rajesh Battala
