← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 868495] Re: [trunk] Sequence refactoring mucks up existing sequences

 

Hello John,

Thanks for your reply!

But this is not a bug it's your migration issue so we are not
considering this.

For this type of issue If you have a maintenance contract with us then
you can contact our OPW team at support@xxxxxxxxxxx thy will definitely
help you.

Thanks.

** Changed in: openobject-server
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/868495

Title:
  [trunk] Sequence refactoring mucks up existing sequences

Status in OpenERP Server:
  Invalid

Bug description:
  Submitting as a bug, though it may be better as a question re:
  migrating existing sequences.

  We're testing the latest updates and it looks the the sequence
  refactoring has caused an issue with existing sequences. Specifically,
  it looks like all sequence 'implementation' are set to 'standard'. For
  existing sequences, this causes an error when it looks for the table
  ir_sequence_XXX, e.g:

   Programming error: relation "ir_sequence_030" does not exist
   LINE 1: SELECT nextval('ir_sequence_030')

  As a workaround, I've set all existing sequences to no_gap instead of
  standard. I'm not sure this is correct, though.

  Thanks.

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


References