You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/07/26 12:25:50 UTC

[jira] [Commented] (CLOUDSTACK-2676) Add Not Null Constraint to UUID columns for cloudstack schema to avoid empty UUID column

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720620#comment-13720620 ] 

Abhinandan Prateek commented on CLOUDSTACK-2676:
------------------------------------------------

Alena/Min can one of you take this up ?
                
> Add Not Null Constraint to UUID columns for cloudstack schema to avoid empty UUID column
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2676
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2676
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Min Chen
>             Fix For: 4.2.0
>
>
> To make sure that we have a consistent upgrade base for all 4.1 customers later, in schema-410to420.sql, we have added sql scripts to populate UUID column of all pre-4.1 schema tables with values from their ID column if UUID column is NULL. To make this work properly, we require that all UUID columns should be populated with values when you add new data into both pre-4.1 schema or post-4.1 schema. To properly enforce this, we should add Not Null constraint at DB level to UUID columns for cloudstack schema. We need to make sure you add those constraints after upgrading the data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira