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

chore(deps): bump sqlalchemy from 1.3.3 to 1.3.9 #244

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link

Bumps sqlalchemy from 1.3.3 to 1.3.9.

Release notes

Sourced from sqlalchemy's releases.

1.3.9

Released: October 4, 2019

  • [engine] [usecase] Added new create_engine() parameter
    create_engine.max_identifier_length. This overrides the
    dialect-coded "max identifier length" in order to accommodate for databases
    that have recently changed this length and the SQLAlchemy dialect has
    not yet been adjusted to detect for that version. This parameter interacts
    with the existing create_engine.label_length parameter in that
    it establishes the maximum (and default) value for anonymously generated
    labels. Additionally, post-connection detection of max identifier lengths
    has been added to the dialect system. This feature is first being used
    by the Oracle dialect.

    References: #4857

  • [oracle] [usecase] The Oracle dialect now emits a warning if Oracle version 12.2 or greater is
    used, and the create_engine.max_identifier_length parameter is
    not set. The version in this specific case defaults to that of the
    "compatibility" version set in the Oracle server configuration, not the
    actual server version. In version 1.4, the default max_identifier_length
    for 12.2 or greater will move to 128 characters. In order to maintain
    forwards compatibility, applications should set
    create_engine.max_identifier_length to 30 in order to maintain
    the same length behavior, or to 128 in order to test the upcoming behavior.
    This length determines among other things how generated constraint names
    are truncated for statements like CREATE CONSTRAINT and DROP CONSTRAINT, which means a the new length may produce a name-mismatch
    against a name that was generated with the old length, impacting database
    migrations.

    References: #4857

  • [sqlite] [usecase] Added support for sqlite "URI" connections, which allow for sqlite-specific
    flags to be passed in the query string such as "read only" for Python
    sqlite3 drivers that support this.

    References: #4863

  • [bug] [tests] Fixed unit test regression released in 1.3.8 that would cause failure for
    Oracle, SQL Server and other non-native ENUM platforms due to new
    enumeration tests added as part of #4285 enum sortability in the
    unit of work; the enumerations created constraints that were duplicated on
    name.

    References: #4285

  • [bug] [oracle] Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a
    SQLAlchemy Date, DateTime or Time datatype is

... (truncated)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

  • Update frequency
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview
Copy link
Author

The following labels could not be found: dependencies.

@m0nhawk m0nhawk closed this Jan 3, 2020
@dependabot-preview
Copy link
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@m0nhawk m0nhawk deleted the dependabot/pip/sqlalchemy-1.3.9 branch January 3, 2020 20:13
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.

None yet

1 participant