xsshunter
                                
                                 xsshunter copied to clipboard
                                
                                    xsshunter copied to clipboard
                            
                            
                            
                        Bump sqlalchemy from 1.0.13 to 1.3.0 in /api
Bumps sqlalchemy from 1.0.13 to 1.3.0.
Release notes
Sourced from sqlalchemy's releases.
1.3.0
Released: March 4, 2019
[feature] [schema] Added new parameters
Table.resolve_fksandMetaData.reflect.resolve_fkswhich when set to False will disable the automatic reflection of related tables encountered inForeignKeyobjects, which can both reduce SQL overhead for omitted tables as well as avoid tables that can't be reflected for database-specific reasons. TwoTableobjects present in the sameMetaDatacollection can still refer to each other even if the reflection of the two tables occurred separately.References: #4517
[feature] [orm] The
Query.get()method can now accept a dictionary of attribute keys and values as a means of indicating the primary key value to load; is particularly useful for composite primary keys. Pull request courtesy Sanjana S.References: #4316
[feature] [orm] A SQL expression can now be assigned to a primary key attribute for an ORM flush in the same manner as ordinary attributes as described in
flush_embedded_sql_expressionswhere the expression will be evaulated and then returned to the ORM using RETURNING, or in the case of pysqlite, works using the cursor.lastrowid attribute.Requires either a database that supports RETURNING (e.g. Postgresql, Oracle, SQL Server) or pysqlite.References: #3133
[bug] [sql] The
Aliasclass and related subclassesCTE,LateralandTableSamplehave been reworked so that it is not possible for a user to construct the objects directly. These constructs require that the standalone construction function or selectable-bound method be used to instantiate new objects.References: #4509
[engine] [feature] Revised the formatting for
StatementErrorwhen stringified. Each error detail is broken up over multiple newlines instead of spaced out on a single line. Additionally, the SQL representation now stringifies the SQL statement rather than usingrepr(), so that newlines are rendered as is. Pull request courtesy Nate Clark.References: #4500
Commits
- See full diff in compare view
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 rebasewill rebase this PR
- @dependabot recreatewill recreate this PR, overwriting any edits that have been made to it
- @dependabot mergewill merge this PR after your CI passes on it
- @dependabot squash and mergewill squash and merge this PR after your CI passes on it
- @dependabot cancel mergewill cancel a previously requested merge and block automerging
- @dependabot reopenwill reopen this PR if it is closed
- @dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- @dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language
- @dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language
- @dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language
- @dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.