c2c-oerpscenario team mailing list archive

[John B <justbe.john@xxxxxxxxx>]

Public bug reported:

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.

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
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:
  New

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