./databases/py-sqlalchemy, Python SQL toolkit and Object Relational Mapper

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.4.48nb1, Package name: py310-sqlalchemy-1.4.48nb1, Maintainer: pkgsrc-users

SQLAlchemy is the Python SQL toolkit and Object Relational Mapper that
gives application developers the full power and flexibility of SQL.

It provides a full suite of well known enterprise-level persistence
patterns, designed for efficient and high-performing database access,
adapted into a simple and Pythonic domain language.


Required to run:
[lang/python310]

Master sites:

Filesize: 8250.97 KB

Version history: (Expand)


CVS history: (Expand)


   2023-07-30 17:32:50 by Adam Ciarcinski | Files touched by this commit (19)
Log message:
Remove dependencies for Python 3.7
   2023-05-12 16:03:10 by Thomas Klausner | Files touched by this commit (1)
Log message:
py-sqlalchemy: add missing dependency

Bump PKGREVISION.
   2023-05-08 23:02:24 by Mark Davies | Files touched by this commit (3) | Package updated
Log message:
py-sqlalchemy: update to 1.4.48

Version 1.4 is taking on a different focus than other SQLAlchemy releases
in that it is in many ways attempting to serve as a potential migration
point for a more dramatic series of API changes currently planned for release
2.0 of SQLAlchemy. The focus of SQLAlchemy 2.0 is a modernized and slimmed
down API that removes lots of usage patterns that have long been discouraged,
as well as mainstreams the best ideas in SQLAlchemy as first class API features,
with the goal being that there is much less ambiguity in how the API is to be
used, as well as that a series of implicit behaviors and rarely-used API flags
that complicate the internals and hinder performance will be removed.
   2022-01-04 21:55:40 by Thomas Klausner | Files touched by this commit (1595)
Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS
   2021-10-26 12:10:08 by Nia Alarie | Files touched by this commit (417)
Log message:
databases: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (some may be only fetched
conditionally):

./databases/cstore/distinfo D6.data.ros.gz
./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz
   2021-10-07 15:35:53 by Nia Alarie | Files touched by this commit (417)
Log message:
databases: Remove SHA1 distfile hashes
   2021-01-18 10:50:36 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-sqlalchemy: updated to 1.3.22

1.3.22

oracle

[oracle] [bug]

Fixed regression which occured due to 5755 which implemented isolation level \ 
support for Oracle. It has been reported that many Oracle accounts don’t \ 
actually have permission to query the v$transaction view so this feature has \ 
been altered to gracefully fallback when it fails upon database connect, where \ 
the dialect will assume “READ COMMITTED” is the default isolation level as \ 
was the case prior to SQLAlchemy 1.3.21. However, explicit use of the \ 
Connection.get_isolation_level() method must now necessarily raise an exception, \ 
as Oracle databases with this restriction explicitly disallow the user from \ 
reading the current isolation level.
   2020-12-18 09:19:28 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-sqlalchemy: updated to 1.3.21

1.3.21

orm

[orm] [bug]

Added a comprehensive check and an informative error message for the case where \ 
a mapped class, or a string mapped class name, is passed to \ 
relationship.secondary. This is an extremely common error which warrants a clear \ 
message.

Additionally, added a new rule to the class registry resolution such that with \ 
regards to the relationship.secondary parameter, if a mapped class and its table \ 
are of the identical string name, the Table will be favored when resolving this \ 
parameter. In all other cases, the class continues to be favored if a class and \ 
table share the identical name.

[orm] [bug]

Fixed bug in Query.update() where objects in the _ormsession.Session that were \ 
already expired would be unnecessarily SELECTed individually when they were \ 
refreshed by the “evaluate”synchronize strategy.

[orm] [bug]

Fixed bug involving the restore_load_context option of ORM events such as \ 
InstanceEvents.load() such that the flag would not be carried along to \ 
subclasses which were mapped after the event handler were first established.

sql

[sql] [bug]

A warning is emmitted if a returning() method such as Insert.returning() is \ 
called multiple times, as this does not yet support additive operation. Version \ 
1.4 will support additive operation for this. Additionally, any combination of \ 
the Insert.returning() and ValuesBase.return_defaults() methods now raises an \ 
error as these methods are mutually exclusive; previously the operation would \ 
fail silently.

[sql] [bug]

Fixed structural compiler issue where some constructs such as MySQL / PostgreSQL \ 
“on conflict / on duplicate key” would rely upon the state of the Compiler \ 
object being fixed against their statement as the top level statement, which \ 
would fail in cases where those statements are branched from a different \ 
context, such as a DDL construct linked to a SQL statement.

postgresql

[postgresql] [usecase]

Added new parameter ExcludeConstraint.ops to the ExcludeConstraint object, to \ 
support operator class specification with this constraint. Pull request courtesy \ 
Alon Menczer.

[postgresql] [bug] [mysql]

Fixed regression introduced in 1.3.2 for the PostgreSQL dialect, also copied out \ 
to the MySQL dialect’s feature in 1.3.18, where usage of a non Table construct \ 
such as text() as the argument to Select.with_for_update.of would fail to be \ 
accommodated correctly within the PostgreSQL or MySQL compilers.

mysql

[mysql] [bug] [reflection]

Fixed issue where reflecting a server default on MariaDB only that contained a \ 
decimal point in the value would fail to be reflected correctly, leading towards \ 
a reflected table that lacked any server default.

[mysql] [sql]

Added missing keywords to the RESERVED_WORDS list for the MySQL dialect: action, \ 
level, mode, status, text, time. Pull request courtesy Oscar Batori.

sqlite

[sqlite] [usecase]

Added sqlite_with_rowid=False dialect keyword to enable creating tables as \ 
CREATE TABLE … WITHOUT ROWID. Patch courtesy Sean Anderson.

mssql

[mssql] [bug]

Fixed bug where a CREATE INDEX statement was rendered incorrectly when both \ 
mssql-include and mssql_where were specified. Pull request courtesy @Adiorz.

[mssql] [bug]

Added SQL Server code “01000” to the list of disconnect codes.

[mssql] [reflection] [sqlite]

Fixed issue with composite primary key columns not being reported in the correct \ 
order. Patch courtesy @fulpm.

oracle

[oracle] [usecase]

Implemented support for the SERIALIZABLE isolation level for Oracle databases, \ 
as well as a real implementation for Connection.get_isolation_level().