Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #529 2 - "This Session's transaction has been rolled back" #531

Merged
merged 8 commits into from
Jun 2, 2016
Merged

Fix #529 2 - "This Session's transaction has been rolled back" #531

merged 8 commits into from
Jun 2, 2016

Commits on May 27, 2016

  1. Created migration to fix the bug

    Luca Albertalli committed May 27, 2016
    Configuration menu
    Copy the full SHA
    6de50b5 View commit details
    Browse the repository at this point in the history
  2. Working also on MySQL

    Luca Albertalli committed May 27, 2016
    Configuration menu
    Copy the full SHA
    29ffe03 View commit details
    Browse the repository at this point in the history

Commits on Jun 1, 2016

  1. Update models.py (#541)

    removing duplicated `user_id` def
    jimexist authored and Luca Albertalli committed Jun 1, 2016
    Configuration menu
    Copy the full SHA
    839fb02 View commit details
    Browse the repository at this point in the history
  2. Added support for Vertica Grains (#515)

    LAlbertalli authored and Luca Albertalli committed Jun 1, 2016
    Configuration menu
    Copy the full SHA
    1ff5304 View commit details
    Browse the repository at this point in the history
  3. i18n: Fix typo in Druid cluster broker port label (#512)

    xrmx authored and Luca Albertalli committed Jun 1, 2016
    Configuration menu
    Copy the full SHA
    e283af9 View commit details
    Browse the repository at this point in the history
  4. Fix #529 1 "This Session's transaction has been rolled back" (#530)

    * Fixing the specific issue
    
    * Added an additional fix for a similar error in #529
    
    Background:
    - When an object is modified by SQLAlchemy, it is invalidated so need to be fetched again from the DB
    - If there's an exception during a transaction, SQLAlchemy performs a rollback and mark the connection as dirty.
    
    Bug:
    - When handling exceptions, the exception handler tries to access the name of the cluster in the main object. Since the name has been invalidated due to a write, SQLAlchemy tries to fetch it on a 'dirty' connection and spits out an error. Solution:
    - Fetch the information for handling the exception before starting the process.
    LAlbertalli authored and Luca Albertalli committed Jun 1, 2016
    Configuration menu
    Copy the full SHA
    1650138 View commit details
    Browse the repository at this point in the history
  5. Modified the migration function to to automatically detect the the fo…

    …reign keys based on the signature.
    
    It supports also sqlite using batch migrations
    Luca Albertalli committed Jun 1, 2016
    Configuration menu
    Copy the full SHA
    938f6cd View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    7308cf6 View commit details
    Browse the repository at this point in the history