codecov[bot]
commented
5 years ago Codecov Report
Merging #83 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #83 +/- ##
======================================
Coverage 2.38% 2.38%
======================================
Files 11 11
Lines 294 294
======================================
Hits 7 7
Misses 287 287Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update e9ff0d1...9998b23. Read the comment docs.
dependabot-preview[bot]
Bumps sqlalchemy from 1.3.6 to 1.3.9.
Release notes
*Sourced from [sqlalchemy's releases](https://github.com/sqlalchemy/sqlalchemy/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](https://github.com/sqlalchemy/sqlalchemy/blob/HEAD/ticket: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](https://github.com/sqlalchemy/sqlalchemy/blob/HEAD/ticket: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](https://github.com/sqlalchemy/sqlalchemy/blob/HEAD/ticket: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](https://github.com/sqlalchemy/sqlalchemy/blob/HEAD/ticket:4285) enum sortability in the > unit of work; the enumerations created constraints that were duplicated on > name. > > References: [#4285](https://github.com/sqlalchemy/sqlalchemy/blob/HEAD/ticket:4285) > > - **[bug] [oracle]** Restored adding cx_Oracle.DATETIME to the setinputsizes() call when a > SQLAlchemy `Date`, `DateTime` or `Time` datatype is > ... (truncated)Commits
- See full diff in [compare view](https://github.com/sqlalchemy/sqlalchemy/commits)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.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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@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 your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)