credativ team mailing list archive

["Stefan Rijnhart \(Therp\)" <948492@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The OU API provides a function for setting default values for any field.
This function currently needs to be called from the post script. The
function works on empty values. However, the ORM sets a default value
for any new field, and it does so before the post script runs. Default
values for new fields that are different from the default value in the
model declaration do not get set.

A notable example is the default value 'no_gap' for existing sequences,
which differs from the default value 'standard' that the model declares.

** Affects: openupgrade-server
     Importance: Medium
         Status: New

** Changed in: openupgrade-server
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of
OpenUpgrade Committers, which is the registrant for OpenUpgrade Server.
https://bugs.launchpad.net/bugs/948492

Title:
  Non-standard default values for new fields do not get set

Status in OpenUpgrade Server:
  New

Bug description:
  The OU API provides a function for setting default values for any
  field. This function currently needs to be called from the post
  script. The function works on empty values. However, the ORM sets a
  default value for any new field, and it does so before the post script
  runs. Default values for new fields that are different from the
  default value in the model declaration do not get set.

  A notable example is the default value 'no_gap' for existing
  sequences, which differs from the default value 'standard' that the
  model declares.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openupgrade-server/+bug/948492/+subscriptions