Magnum

The nullable parameter is not necessary

Bug #1476068 reported by Hua Wang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Hua Wang
Magnum mitaka-1

Bug Description

The default of the nullable parameter in sqlalchemy Column class is true. So we don't need to use the parameter when we need a nullable column.

Hua Wang (humble00)
Changed in magnum:
assignee: nobody → Hua Wang (humble00)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/203471

Changed in magnum:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/203471
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=5da90842b724aae6037bae5d5f66f69e37625b6f
Submitter: Jenkins
Branch: master

commit 5da90842b724aae6037bae5d5f66f69e37625b6f
Author: Wanghua <email address hidden>
Date: Mon Jul 20 19:22:39 2015 +0800

    The nullable parameter is not necessary

    The default of the nullable parameter in sqlalchemy Column class
    is true. So we don't need to use the parameter when we need a
    nullable column.

    Change-Id: I08097025e8894657bfca8843fed3c1c78797b8c3
    Closes-Bug: 1476068

Changed in magnum:
status: In Progress → Fix Committed
Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.