Skip to content

Conversation

@KnightMurloc
Copy link
Collaborator

The following points have been fixed:

  1. PyGreSQL 5 has added support for converting additional data types.
    Analyzedb: Converting datetime to a string for correct comparison with the value
    saved in the file.
    el8_migrate_localte.py, gparray.py, gpcatalog.py and gpcheckcat: using the Bool
    type instead of comparing with a string.
    gpcheckcat, repair_missing_extraneous.py and unique_index_violation_check:
    using python list instead of string parsing.
  2. PyGreSQL 5 added support for closing a connection when using the with
    construct. Because of this, in a number of places, reading from the cursor took
    place after the connection was closed.
  3. PyGreSQL 5 does not end the transaction if an error occurs, which leads to a
    possible connection leak if an error occurs in the connect function. So catch
    errors that happen in the connect function.
  4. Add closure of the connection saved in context after the scenario in behave
    tests.
  5. Add closure to the connection if it does not return from the function.
  6. Use the python wrapper for the connect function instead of C one.
  7. Use a custom cursor to disable row postprocessing to avoid fixing a large
    amount of code.

The following points have been fixed:
1. PyGreSQL 5 has added support for converting additional data types.
Analyzedb: Converting datetime to a string for correct comparison with the value
saved in the file.
el8_migrate_localte.py, gparray.py, gpcatalog.py and gpcheckcat: using the Bool
type instead of comparing with a string.
gpcheckcat, repair_missing_extraneous.py and unique_index_violation_check:
using python list instead of string parsing.
2. PyGreSQL 5 added support for closing a connection when using the with
construct. Because of this, in a number of places, reading from the cursor took
place after the connection was closed.
3. PyGreSQL 5 does not end the transaction if an error occurs, which leads to a
possible connection leak if an error occurs in the connect function. So catch
errors that happen in the connect function.
4. Add closure of the connection saved in context after the scenario in behave
tests.
5. Add closure to the connection if it does not return from the function.
6. Use the python wrapper for the connect function instead of C one.
7. Use a custom cursor to disable row postprocessing to avoid correcting a large
amount of code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants