codecov[bot]
commented
4 years ago Codecov Report
Merging #98 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #98 +/- ##
======================================
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 66aa0e5...a90d5f5. Read the comment docs.
dependabot-preview[bot]
Bumps sqlalchemy from 1.3.10 to 1.3.11.
Release notes
*Sourced from [sqlalchemy's releases](https://github.com/sqlalchemy/sqlalchemy/releases).* > > # 1.3.11 > > Released: November 11, 2019 > ## orm > > > - **[orm] [usecase]** Added accessor `Query.is_single_entity()` to `Query`, which > will indicate if the results returned by this `Query` will be a > list of ORM entities, or a tuple of entities or column expressions. > SQLAlchemy hopes to improve upon the behavior of single entity / tuples in > future releases such that the behavior would be explicit up front, however > this attribute should be helpful with the current behavior. Pull request > courtesy Patrick Hayes. > > References: [#4934](http://www.sqlalchemy.org/trac/ticket/4934) > > - **[orm] [bug]** The `relationship.omit_join` flag was not intended to be > manually set to True, and will now emit a warning when this occurs. The > omit_join optimization is detected automatically, and the `omit_join` > flag was only intended to disable the optimization in the hypothetical case > that the optimization may have interfered with correct results, which has > not been observed with the modern version of this feature. Setting the > flag to True when it is not automatically detected may cause the selectin > load feature to not work correctly when a non-default primary join > condition is in use. > > References: [#4954](http://www.sqlalchemy.org/trac/ticket/4954) > > - **[orm] [bug]** A warning is emitted if a primary key value is passed to `Query.get()` > that consists of None for all primary key column positions. Previously, > passing a single None outside of a tuple would raise a `TypeError` and > passing a composite None (tuple of None values) would silently pass > through. The fix now coerces the single None into a tuple where it is > handled consistently with the other None conditions. Thanks to Lev > Izraelit for the help with this. > > References: [#4915](http://www.sqlalchemy.org/trac/ticket/4915) > > - **[orm] [bug]** The `BakedQuery` will not cache a query that was modified by a > `QueryEvents.before_compile()` event, so that compilation hooks that > may be applying ad-hoc modifications to queries will take effect on each > run. In particular this is helpful for events that modify queries used in > lazy loading as well as eager loading such as "select in" loading. In > order to re-enable caching for a query modified by this event, a new > flag `bake_ok` is added; see `baked_with_before_compile` for > details. > > A longer term plan to provide a new form of SQL caching should solve this > kind of issue more comprehensively. > ... (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)