id in the upgrade prevents exactly the problem you've
> >described. That's why we're doing it.
> >
> >
> >--Alex
> >
> >> -Original Message-
> >> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> >> Sent: Thursday, May 23, 2
ee that for some tables there
>> >is a NOT NULL constraint.
>> >
>> >-Koushik
>> >
>> >> -Original Message-
>> >> From: Min Chen [mailto:min.c...@citrix.com]
>> >> Sent: Friday, May 24, 2013 4:09 AM
>> >> To:
..@citrix.com]
> Sent: Thursday, May 23, 2013 11:09 PM
> To: dev@cloudstack.apache.org
> Subject: Re: Convention on UUID column
>
> Agree with Koushik. Lets enforce the not null constraint on all the UUID
> fields
> now that we are populating it.
>
> Also wanted to as
les there is
>a NOT NULL constraint.
>
>-Koushik
>
>> -Original Message-
>> From: Min Chen [mailto:min.c...@citrix.com]
>> Sent: Friday, May 24, 2013 4:09 AM
>> To: dev@cloudstack.apache.org
>> Subject: Convention on UUID column
>>
>> Hi the
les there is
>a NOT NULL constraint.
>
>-Koushik
>
>> -Original Message-
>> From: Min Chen [mailto:min.c...@citrix.com]
>> Sent: Friday, May 24, 2013 4:09 AM
>> To: dev@cloudstack.apache.org
>> Subject: Convention on UUID column
>>
>> Hi there,
3 4:09 AM
> To: dev@cloudstack.apache.org
> Subject: Convention on UUID column
>
> Hi there,
>
> During API refactoring efforts, Rohit and I run into several issues due to
> empty UUID column for existing DB entries. Since UUID was introduced later
> in 3.0.x, we have to alw
Hi there,
During API refactoring efforts, Rohit and I run into several issues due to
empty UUID column for existing DB entries. Since UUID was introduced later in
3.0.x, we have to always conditionally handle existing customers with empty
UUID columns for different entities, causing much headac
