sqlalchemy-tickets Mailing List for SQLAlchemy (Page 76)
Brought to you by:
zzzeek
Menu
▾
▴
sqlalchemy-tickets — trac tickets and updates forwarded to this list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(174) |
Apr
(50) |
May
(71) |
Jun
(129) |
Jul
(113) |
Aug
(141) |
Sep
(82) |
Oct
(142) |
Nov
(97) |
Dec
(72) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(159) |
Feb
(213) |
Mar
(156) |
Apr
(151) |
May
(58) |
Jun
(166) |
Jul
(296) |
Aug
(198) |
Sep
(89) |
Oct
(133) |
Nov
(150) |
Dec
(122) |
| 2008 |
Jan
(144) |
Feb
(65) |
Mar
(71) |
Apr
(69) |
May
(143) |
Jun
(111) |
Jul
(113) |
Aug
(159) |
Sep
(81) |
Oct
(135) |
Nov
(107) |
Dec
(200) |
| 2009 |
Jan
(168) |
Feb
(109) |
Mar
(141) |
Apr
(128) |
May
(119) |
Jun
(132) |
Jul
(136) |
Aug
(154) |
Sep
(151) |
Oct
(181) |
Nov
(223) |
Dec
(169) |
| 2010 |
Jan
(103) |
Feb
(209) |
Mar
(201) |
Apr
(183) |
May
(134) |
Jun
(113) |
Jul
(110) |
Aug
(159) |
Sep
(138) |
Oct
(96) |
Nov
(116) |
Dec
(94) |
| 2011 |
Jan
(97) |
Feb
(188) |
Mar
(157) |
Apr
(158) |
May
(118) |
Jun
(102) |
Jul
(137) |
Aug
(113) |
Sep
(104) |
Oct
(108) |
Nov
(91) |
Dec
(162) |
| 2012 |
Jan
(189) |
Feb
(136) |
Mar
(153) |
Apr
(142) |
May
(90) |
Jun
(141) |
Jul
(67) |
Aug
(77) |
Sep
(113) |
Oct
(68) |
Nov
(101) |
Dec
(122) |
| 2013 |
Jan
(60) |
Feb
(77) |
Mar
(77) |
Apr
(129) |
May
(189) |
Jun
(155) |
Jul
(106) |
Aug
(123) |
Sep
(53) |
Oct
(142) |
Nov
(78) |
Dec
(102) |
| 2014 |
Jan
(143) |
Feb
(93) |
Mar
(35) |
Apr
(26) |
May
(27) |
Jun
(41) |
Jul
(45) |
Aug
(27) |
Sep
(37) |
Oct
(24) |
Nov
(22) |
Dec
(20) |
| 2015 |
Jan
(17) |
Feb
(15) |
Mar
(34) |
Apr
(55) |
May
(33) |
Jun
(31) |
Jul
(27) |
Aug
(17) |
Sep
(22) |
Oct
(26) |
Nov
(27) |
Dec
(22) |
| 2016 |
Jan
(20) |
Feb
(24) |
Mar
(23) |
Apr
(13) |
May
(17) |
Jun
(14) |
Jul
(31) |
Aug
(23) |
Sep
(24) |
Oct
(31) |
Nov
(23) |
Dec
(16) |
| 2017 |
Jan
(24) |
Feb
(20) |
Mar
(27) |
Apr
(24) |
May
(28) |
Jun
(18) |
Jul
(18) |
Aug
(23) |
Sep
(30) |
Oct
(17) |
Nov
(12) |
Dec
(12) |
| 2018 |
Jan
(27) |
Feb
(23) |
Mar
(13) |
Apr
(19) |
May
(21) |
Jun
(29) |
Jul
(11) |
Aug
(22) |
Sep
(14) |
Oct
(9) |
Nov
(24) |
Dec
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 22:33:52
|
#2837: Logging FAQ suggestion
---------------------------+-----------------------------------------
Reporter: jonathan | Owner: zzzeek
Type: enhancement | Status: new
Priority: lowest | Milestone:
Component: documentation | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
---------------------------+-----------------------------------------
The FAQ on logging
http://docs.sqlalchemy.org/en/rel_0_8/faq.html?highlight=logging#how-
do-i-configure-logging
sent me to the Engine logging docs:
http://docs.sqlalchemy.org/en/rel_0_8/core/engines.html#dbengine-
logging
I wanted to suggest this addition to the docs :
-------
Sometimes you might want to disable existing query logging for certain
statements, such as when you are inserting a BLOB or large TEXT value.
An easy way to accomplish this is to wrap your query in a pair of
statements
that toggle the `disabled` attribute of the logger.
In the example below, note that the logger needed to disable already-
enabled
query logging is `sqlalchemy.engine.base.Engine` , and not the
`sqlalchemy.engine` logger mentioned above.
import logging
logging.getLogger('sqlalchemy.engine.base.Engine').disabled = True
... execute query ...
logging.getLogger('sqlalchemy.engine.base.Engine').disabled = False
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2837>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 20:28:19
|
#2836: supply distinct within subq eager load when we see that the inner query
isn't loading a distinct field
--------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.0
Component: orm | Severity: minor - half an hour
Keywords: | Progress State: in progress
--------------------+---------------------------------------
see https://github.com/zzzeek/sqlalchemy/pull/33 for current work on this.
proposed patch:
{{{
#!diff
diff --git a/lib/sqlalchemy/orm/strategies.py
b/lib/sqlalchemy/orm/strategies.py
index 6ca737c..23e8cb6 100644
--- a/lib/sqlalchemy/orm/strategies.py
+++ b/lib/sqlalchemy/orm/strategies.py
@@ -767,8 +767,17 @@ class SubqueryLoader(AbstractRelationshipLoader):
if not q._from_obj and entity_mapper.isa(leftmost_mapper):
q._set_select_from([entity_mapper], False)
+ target_cols = q._adapt_col_list(leftmost_attr)
+
# select from the identity columns of the outer
- q._set_entities(q._adapt_col_list(leftmost_attr))
+ q._set_entities(target_cols)
+
+ # if target_cols refer to a non-primary key or only
+ # part of a composite primary key, set the q as distinct
+ for c in target_cols:
+ if not set(target_cols).issuperset(c.table.primary_key):
+ q._distinct = True
+ break
if q._order_by is False:
q._order_by = leftmost_mapper.order_by
}}}
we'll try to backport an "experimental" version of this to 0.8/0.7.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2836>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 19:40:47
|
#2835: set index attributes before events are called
---------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.0
Component: schema | Severity: minor - half an hour
Keywords: | Progress State: needs tests
---------------------+---------------------------------------
{{{
#!diff
diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index 92220b0..a8b60e0 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -2600,14 +2600,14 @@ class Index(ColumnCollectionMixin, SchemaItem):
columns.append(expr)
self.expressions = expressions
+ self.name = quoted_name(name, kw.pop("quote", None))
+ self.unique = kw.pop('unique', False)
+ self.kwargs = kw
# will call _set_parent() if table-bound column
# objects are present
ColumnCollectionMixin.__init__(self, *columns)
- self.name = quoted_name(name, kw.pop("quote", None))
- self.unique = kw.pop('unique', False)
- self.kwargs = kw
def _set_parent(self, table):
ColumnCollectionMixin._set_parent(self, table)
}}}
else impossible to use parent attach events for an inline index to set up
name
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2835>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 16:53:08
|
#2748: fix default argument of None for
DefaultDialect.reflecttable->exclude_columns, should be ()
-----------------------------------+-----------------------------------
Reporter: rstuart4133 | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.9.0
Component: schema | Severity: trivial - <10 minutes
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-----------------------------------
Changes (by zzzeek):
* status: new => closed
* milestone: 0.8.xx => 0.9.0
* resolution: => fixed
* status_field: in queue => completed/closed
Comment:
r5f0b864ad02409cf668fa7db in 0.9 makes both include/exclude arguments
mandatory, the Dialect.reflecttable method is not even needed at this
point, though I'm leaving it in as an alternative for 3rd party dialects
in rare circumstances.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2748#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 16:27:52
|
#2808: AssociationProxy should use keywords on create
-----------------------------------+----------------------------------
Reporter: schlamar | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: ext | Severity: minor - half an hour
Resolution: wontfix | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: reopened => closed
* resolution: => wontfix
Comment:
if the proposal is to have association proxy generate "relationship()"
automatically, we can't do that. if the proposal is to have the implicit
"creator" do kw arguments instead of positional, I think it's too late to
change it like that and simple recipes can work around it. I'd accept
more documentation here.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2808#comment:15>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-11 16:20:37
|
#2820: session.merge/nullable primary keys - FlushError: Can't update table using
NULL for primary key value
-----------------------------------+-------------------------------
Reporter: elsdoerfer | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: orm | Severity: major - 1-3 hours
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => worksforme
* status_field: needs questions answered => completed/closed
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2820#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-09 08:47:50
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: medium | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by lyschoening):
* cc: lars@… (added)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:13>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-09 00:09:30
|
#2815: any way to detect this cycle?
-----------------------------------+----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.8.xx
Component: sql | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in queue => completed/closed
Comment:
re488bb47e4bd21ff0a09ce23e1adf00ba64d5d57 0.8
re74627f827542044c1d2087be95e41d4b1b46f24 master
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2815#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-08 23:50:15
|
#2813: Buglette with annotated join condition
-----------------------------------+----------------------------------
Reporter: dairiki | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.8.xx
Component: orm | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: needs tests => completed/closed
Comment:
r79f55eb20bf3b65bf0663cf96de96c68f8804399 0.8
r9df4651fba6d1cd3d2b490f58263cc45a81788f4 master
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2813#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-08 23:26:41
|
#2831: ForeignKey has a bogus "schema" argument
-----------------------------------+----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: highest | Milestone: 0.8.xx
Component: schema | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in queue => completed/closed
Comment:
rc1a69ab841e728061dd890dd02e6ce6be2970473
rf27b7551292fcd0230effc3387b86ac5a544a561
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2831#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 16:58:07
|
#2824: Add ability to query column sets as one entity
-----------------------------------+-------------------------------
Reporter: vmagamedov | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Comment (by vmagamedov):
Dreams comes true, thank you very much! :)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2824#comment:16>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 16:54:09
|
#2824: Add ability to query column sets as one entity
-----------------------------------+-------------------------------
Reporter: vmagamedov | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: reopened => closed
* resolution: => fixed
* status_field: in progress => completed/closed
Comment:
its an option in rd47a376863bd7c804e439680.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2824#comment:15>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 14:58:21
|
#2824: Add ability to query column sets as one entity
------------------------------+-------------------------------
Reporter: vmagamedov | Owner: zzzeek
Type: enhancement | Status: reopened
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in progress |
------------------------------+-------------------------------
Changes (by zzzeek):
* status: closed => reopened
* resolution: fixed =>
* status_field: completed/closed => in progress
Comment:
I thought about that. The single model thing has always bothered me in
its inconsistency. but i guess people will probably expect it to work
that way, will look into it (it's just a conditional somewhere).
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2824#comment:14>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 14:43:02
|
#1418: Flexible deferred interface
-----------------------------------+--------------------------------------
Reporter: guest | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: 0.9.0
Component: orm | Severity: refactor - over two days
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+--------------------------------------
Comment (by kentbower):
thanks for the truly excellent software
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1418#comment:15>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 08:21:55
|
#2824: Add ability to query column sets as one entity
-----------------------------------+-------------------------------
Reporter: vmagamedov | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Comment (by vmagamedov):
> Other tests failed because bundles can't be selected as "single entity".
I think that bundles can work like models: when you querying only one
bundle, query should yield bundles and not keyed tuples with one bundle.
{{{#!python
points = db.session.query(Bundle(Point.x, Point.y)).all()
for point in points:
print point.x, point.y
}}}
Is this possible to implement? At least optionally (overridable in Bundle
subclass)?
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2824#comment:13>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-07 00:30:41
|
#1418: Flexible deferred interface
-----------------------------------+--------------------------------------
Reporter: guest | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: 0.9.0
Component: orm | Severity: refactor - over two days
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+--------------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* severity: major - 1-3 hours => refactor - over two days
* status_field: in queue => completed/closed
Comment:
it's taken me weeks and weeks to get this all done -
r1b25ed907fb7311d28d2273c9b9858b.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1418#comment:14>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-06 04:05:14
|
#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.6.xx
Component: postgres | Severity: no triage selected yet
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by zzzeek):
Hm I guess he merged it after I had done the extra work? I might have
still been getting used to pull requests at that point.
for Py2/3, the only rational choice is an in-place codebase. all of my
major libs/tools are now py2k/3k in place, no 2to3 needed - alembic,
dogpile, mako, sqlalchemy as of 0.9. mako in fact supports from py2.4 all
the way to py3.4, and is very heavy on unicode as well as python
interpreter internals even. It's not very hard to make a pure-python
codebase support between 2 and 3.
the two paramstyles I think are important, and the ones we've decided on
the DB-SIG list would be the standard in a DBAPI 3, are qmark and named.
These two formats are commonplace outside of the Python world.
my next choice would be format and pyformat. I'm not too keen on
numbered since it is just another named style, just more awkward.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:10>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-06 03:49:05
|
#2834: regression due to #2812 regarding anon labels
-----------------------------------+----------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.9.0
Component: orm | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* severity: major - 1-3 hours => minor - half an hour
* status_field: in queue => completed/closed
Comment:
rd79e1d69a6b2d0d1cc18d3d9d0283ef
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2834#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-06 03:03:18
|
#2834: regression due to #2812 regarding anon labels
---------------------------+-------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
specifically when quote is non-None we get un-converted labels:
"A_1"."A" AS "%(4318554768 A)s_A"
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2834#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-06 03:02:02
|
#2834: regression due to #2812 regarding anon labels
---------------------------+-------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Changes (by zzzeek):
* severity: no triage selected yet => major - 1-3 hours
* status_field: awaiting triage => in queue
* milestone: => 0.9.0
Comment:
OK this is 0.9 only and is a regression due to #2812 /
r031ef0807838842a827135dbace760.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2834#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-05 19:14:55
|
#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.6.xx
Component: postgres | Severity: no triage selected yet
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by tlocke):
This is interesting. Looking at
https://github.com/zzzeek/pg8000/compare/mfenniak:trunk...trunk it seems
that @mfenniak did accept all your changes. I checked, and all your work
is in the HEAD of 'trunk' on the mfenniak repo.
I too have been working on speeding up PG8000, but all of my stuff has
been on the Python 3 version. The two branches were very different when I
started, and now they've diverged even more. It's a shame that the two
versions have divided our efforts. I've not sure what the accepted
strategy is for maintaining Python 2 and 3 libraries, do you have any
views?
Having worked on the speed for py3, I'm now focussing on fixing bugs. With
bugs I've taken the approach of doing the fix to both trunk and py3
branches.
Btw, I had a similar thought to you about simplifying the paramstyles.
I've put my suggestion for DBAPI 3 at:
https://github.com/tlocke/pg8000/tree/three
It removes the 'paramstyle' attribute entirely and just has parameter
labels as :1, :2, :3, ... or the :name style. If it can cast the label to
an int, it assumes the parameters argument is a sequence, otherwise it
assumes it's a mapping. What do you think?
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:9>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-05 12:04:24
|
#2834: eagerload fails when quote=False is used on tables and columns
--------------------+-----------------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone:
Component: orm | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
--------------------+-----------------------------------------
If quote=False is used, a query which has some eagerload-configured
relationship fails.
Attached is a simple case which exercises the error. It has been tested on
SQLite and also on PostgreSQL.
Note that the case performs well if q=None (the SQLAlchemy default) or
q=True are used.
Regards,
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2834>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-03 21:30:34
|
#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.6.xx
Component: postgres | Severity: no triage selected yet
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by zzzeek):
great. not sure if you're aware, I created a fork of pg8000 that made
extensive changes to the internals in the efforts of lots more speed and
also extension capability. It was specific to a database I was contracted
to work with called Akiban, but the thrust of the internal changes was to
do away with most of the internal object creation pg8000 uses in order to
represent postgres structures. I had emailed Mathieu about it but he
did not respond. the fork is at https://github.com/zzzeek/pg8000/ ,
examples of major reductions in object creation can be seen at
https://github.com/zzzeek/pg8000/commit/fffc22a5b92d849a23df8f46d1c54d3e98e9fba4,
https://github.com/zzzeek/pg8000/commit/bc9127429b1a9df192d782198aee16488da0962f
and
https://github.com/zzzeek/pg8000/commit/b59841124f474fe14c69f7ff671e98f814447717
where I tackle that huge parameter formatting function, it looks like you
might have addressed this as well. I have it supporting just the two
formats that psycopg2 does instead of all of them.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:8>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-03 21:15:00
|
#1631: pg8000 not working with enums.
-----------------------------------+------------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.6.xx
Component: postgres | Severity: no triage selected yet
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by tlocke):
I've actually committed a fix to PG8000 that doesn't require any casting
in the SQL
https://github.com/mfenniak/pg8000/commit/41362eed49a271da05a079b953f7b513ad0483e2.
So no change needed to SQLAlchemy!
Btw, to answer your question above about the 'e', I was following the
@percious example which confusingly gave the same name 'e' to the column
and the enum type:
{{{
Column(u'e', Enum('one', 'two', name=u'e'))
}}}
Anyway, that's by the by.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1631#comment:7>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-03 21:09:18
|
#2824: Add ability to query column sets as one entity
-----------------------------------+-------------------------------
Reporter: vmagamedov | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: orm | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in progress => completed/closed
Comment:
more fixes to composites and all I think this is pretty good, merged in
ra83378b64005971fe97dff270641bce.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2824#comment:12>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
186 messages has been excluded from this view by a project administrator.
