Which file to update for schema change required for 4.1.1?

[Min Chen <mi...@citrix.com>]

Hi there,

I need to fix a bug for 4.1.1, which requires some schema change. Two existing files (schema-40to410.sql and schema-410to420.sql) seem not fit here. In this case, should we create a new schema-410to411.sql for this purpose? Also, for fix required for 4.1.1, can we directly check into 4.1 branch or is it still a controlled checkin?
Thanks for clarification.

-min

RE: Which file to update for schema change required for 4.1.1?

[Koushik Das <ko...@citrix.com>]

Ideally if the fix involves schema changes then it should go to 4.2. If there is no alternative then 410to411.sql looks like the option. But then the upgrade path becomes complicated. The following needs to be handled 4.1.0 -> 4.2.0, 4.1.1 -> 4.2.0. Or else the upgrade sql script needs to be guarded with "if exists" kind of clause for every schema change so that a single 4.1 -> 4.2 script suffices.

-Koushik

> -----Original Message-----
> From: Min Chen [mailto:min.chen@citrix.com]
> Sent: Wednesday, June 19, 2013 10:14 PM
> To: dev@cloudstack.apache.org
> Subject: Which file to update for schema change required for 4.1.1?
> 
> Hi there,
> 
> I need to fix a bug for 4.1.1, which requires some schema change. Two
> existing files (schema-40to410.sql and schema-410to420.sql) seem not fit
> here. In this case, should we create a new schema-410to411.sql for this
> purpose? Also, for fix required for 4.1.1, can we directly check into 4.1 branch
> or is it still a controlled checkin?
> Thanks for clarification.
> 
> -min

Re: Which file to update for schema change required for 4.1.1?

[Chip Childers <ch...@sungard.com>]

Adding that 410to411 file was on my list of things to get done, but go
ahead and do it.  We also need the DB upgrade maps to be updated to
include it (as well as on master for 4.2).

The branch is not "controlled"...  so go for it!

-chip

On Wed, Jun 19, 2013 at 04:43:12PM +0000, Min Chen wrote:
> Hi there,
> 
> I need to fix a bug for 4.1.1, which requires some schema change. Two existing files (schema-40to410.sql and schema-410to420.sql) seem not fit here. In this case, should we create a new schema-410to411.sql for this purpose? Also, for fix required for 4.1.1, can we directly check into 4.1 branch or is it still a controlled checkin?
> Thanks for clarification.
> 
> -min
>