OK, thanks, Min.

I didn't notice both (seemingly redundant) commands at first and so only
put my code in the first one.

When I didn't see my new columns show up, I had to dig a bit and found
there was similar code below.

Once I updated that code instead, everything works as I expected.


On Thu, May 23, 2013 at 2:15 PM, Min Chen <min.c...@citrix.com> wrote:

> It is related to this commit d1642a489ce76e055d60b2caf3ccfe4bb136b745.
> Schema-410to420.sql should have one section to define the new volume_view
> for 4.2.0.
> CC Nitin here to see if his new volume_view should be used or the one
> before his commit in this file.
>
> THanks
> -min
>
>
> On 5/23/13 12:50 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com>
> wrote:
>
> >Hi,
> >
> >I've added a few fields (min, max, burst IOPS) to two tables and - in the
> >process - noticed the following view is dropped and created twice:
> >
> >DROP VIEW IF EXISTS `cloud`.`volume_view`;
> >CREATE VIEW `cloud`.`volume_view` AS
> >
> >I assume this is a bug and have removed (in my sandbox) the
> >first occurrence.
> >
> >If anyone knows of a reason why we want to keep this code as is, please
> >let
> >me know as this change will otherwise be submitted when I submit my code
> >for review tomorrow or early next week.
> >
> >Thanks!
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>
> >* *
>
>


-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Reply via email to