Skip to content

bug: sequence allocation algorithm has global, shared state #16

Closed
Closed
bug: sequence allocation algorithm has global, shared state#16

Description

@bartoszwalacik
bartoszwalacik
opened on Jan 31, 2016

since class KeyGeneratorRegistry has static map of SequenceAllocation objects,
current val of each sequence is global.

It means that new instance of PolyJDBC, feeded with new db connection, doesnt initiates
current states of sequences from db but takes stale values (possibly genereted for another database).

it causes pk vilation exceptions.

Activity

  1. adamdubiel
    added 4 commits that reference this issue on Jan 31, 2016

    fixing #16 - one sequence generator per PolyJDBC instance

    fca8724

    fixing #16 - one sequence generator per PolyJDBC instance

    3c12d5d

    fixing #16 - one sequence generator per PolyJDBC instance

    5c6ae1a

    fixing #16 - one sequence generator per PolyJDBC instance

    927ce5c
  2. bartoszwalacik
    added a commit that references this issue on Feb 1, 2016

    Merge pull request #17 from polyjdbc/16_key_generator_per_instances

    9d63b3e
  3. adamdubiel
    closed this as completedon Feb 1, 2016

  4. adamdubiel commented on Feb 1, 2016

    @adamdubiel
    adamdubiel
    on Feb 1, 2016
    Member

    Fixed & release: 0.6.1

  5. bartoszwalacik commented on Feb 1, 2016

    @bartoszwalacik
    bartoszwalacik
    on Feb 1, 2016
    ContributorAuthor

    thanks a lot for this super fast fix !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions