sqlalchemy-tickets Mailing List for SQLAlchemy (Page 73)
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-24 05:01:50
|
#2851: Sqlalchemy does not work in ipv6 environment
-----------------------------------+-------------------------------
Reporter: huwei | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.7.xx
Component: engine | Severity: major - 1-3 hours
Resolution: fixed | Keywords: ipv6 mysql
Progress State: completed/closed |
-----------------------------------+-------------------------------
Comment (by huwei):
I have tried it, it does work. Thanks.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2851#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-24 01:33:16
|
#2851: Sqlalchemy does not work in ipv6 environment
-----------------------------------+-------------------------------
Reporter: huwei | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.7.xx
Component: engine | Severity: major - 1-3 hours
Resolution: fixed | Keywords: ipv6 mysql
Progress State: completed/closed |
-----------------------------------+-------------------------------
Comment (by huwei):
Replying to [comment:2 zzzeek]:
> this change is trivial so it's back to 0.7:
>
> r470133b5ec589b80f4a533af870370313580544c 0.7
>
> r785e44c48be5a25a71b2f2d4fe5e5219ffcb93a8 0.8
>
> r382cd56772efd92a9fe5ce46623029a04163c8cf master
Thanks for your quick response, I'll try your patch.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2851#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-24 00:01:32
|
#2852: errors in return_defaults() docs
---------------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.0
Component: documentation | Severity: minor - half an hour
Keywords: | Progress State: in queue
---------------------------+---------------------------------------
1. link to ResultProxy.server_returned_default or
ResultProxy.returned_defaults listed in two different ways and neither is
linked
2. the paragraph about "single-row executions" is wrong, this needs to be
changed to refer to "executemany" executions not being supported by most
DBAPIs. The RETURNING DBAPIs except for oracle support multiple row
UPDATE and DELETE statements. the doc here should be modified to talk
more about intent (fetching defaults for a single-row INSERT/UPDATE vs.
fetching N number of rows for single execution INSERT/UPDATE/DELETE).
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2852>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:52:08
|
#2823: clarify docs regarding true()/false() constants, that these are not fully
compatible on many backends
-----------------------------------+----------------------------------
Reporter: leavittx | Owner:
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: mssql | Severity: minor - half an hour
Resolution: duplicate | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Comment (by zzzeek):
this is all completed, so that true/false work in as many cases as
possible (with "IS" still being one that isn't going to work cross-
platform at the moment). true/false will be factored out of and/or, or
will flatten out other elements, and will also render as `1 = 1` or `0 =
1` on non-boolean backends, we'll see how that goes. If true/false aren't
used then you never see their effects.
please see
http://docs.sqlalchemy.org/en/latest/changelog/migration_09.html#improved-
rendering-of-boolean-constants-null-constants-conjunctions.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2823#comment:9>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:48:43
|
#2804: coerce_to_bool for where(), having(), etc.
-----------------------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: sql | Severity: very major - up to 2 days
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+---------------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* severity: major - 1-3 hours => very major - up to 2 days
* status_field: in queue => completed/closed
Comment:
rf035b6e0a41238d092ea2dd
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2804#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:48:29
|
#2804: coerce_to_bool for where(), having(), etc.
------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Comment (by zzzeek):
also #2739 affected.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2804#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:20:49
|
#2501: the DELETE before INSERT problem
------------------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.xx
Component: orm | Severity: very major - up to 2 days
Resolution: | Keywords:
Progress State: needs tests |
------------------------------+---------------------------------------
Changes (by zzzeek):
* milestone: 0.9.0 => 0.9.xx
Comment:
this is very ready to go if it has tests, but 0.9 is way behind sched at
this point so pushing this to 0.9.xx since it has minimal impact on
existing code
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2501#comment:10>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 21:18:32
|
#1390: postgresql regular expression operators
------------------------------+----------------------------------
Reporter: guest | Owner: zzzeek
Type: enhancement | Status: new
Priority: medium | Milestone: 0.9.xx
Component: postgres | Severity: minor - half an hour
Resolution: | Keywords: match
Progress State: needs tests |
------------------------------+----------------------------------
Changes (by zzzeek):
* milestone: 0.9.0 => 0.9.xx
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1390#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 20:55:55
|
#2804: coerce_to_bool for where(), having(), etc.
------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Comment (by zzzeek):
also #2739 affected
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2804#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 19:04:02
|
#2851: Sqlalchemy does not work in ipv6 environment
-----------------------------------+-------------------------------
Reporter: huwei | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.7.xx
Component: engine | Severity: major - 1-3 hours
Resolution: fixed | Keywords: ipv6 mysql
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* status_field: in progress => completed/closed
* resolution: => fixed
* milestone: 0.8.xx => 0.7.xx
Comment:
this change is trivial so it's back to 0.7:
r470133b5ec589b80f4a533af870370313580544c 0.7
r785e44c48be5a25a71b2f2d4fe5e5219ffcb93a8 0.8
r382cd56772efd92a9fe5ce46623029a04163c8cf master
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2851#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 15:43:25
|
#2851: Sqlalchemy does not work in ipv6 environment
------------------------------+-------------------------------
Reporter: huwei | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.8.xx
Component: engine | Severity: major - 1-3 hours
Resolution: | Keywords: ipv6 mysql
Progress State: in progress |
------------------------------+-------------------------------
Changes (by zzzeek):
* owner: => zzzeek
* milestone: 0.7.xx => 0.8.xx
* component: mysql => engine
* severity: refactor - over two days => major - 1-3 hours
* status_field: awaiting triage => in progress
Comment:
will have to see if we can just use urlparse() for that parsing. the
workaround for now would be to instantiate a URL() object directly, though
you'd have to bypass openstack's configuration system for that.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2851#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-23 08:19:59
|
#2851: Sqlalchemy does not work in ipv6 environment
------------------------+-------------------------------------------
Reporter: huwei | Owner:
Type: defect | Status: new
Priority: high | Milestone: 0.7.xx
Component: mysql | Severity: refactor - over two days
Keywords: ipv6 mysql | Progress State: awaiting triage
------------------------+-------------------------------------------
Environment:
python 2.6
sqlalchemy 0.7.9
redhat 6.4
mysql 5.5.34
In openstack grizzly version, I configured the mysql connection url from
ipv4 to ipv6
address(connection=mysql://keystone:keystone@[2001:da8:2004:1000:202:116:160:90]/keystone?charset=utf).
And restart openstack service, but when I use keystone cli to list users.
I got an error message "Authorization Failed: KS-117430E An unexpected
error prevented the server from fulfilling your request. invalid literal
for int() with base 10: 'da8:2004:1000:202:116:160:90]' (HTTP 500)".
And the following is the error log information.
2013-10-21 08:14:57.429 25606 ERROR keystone.common.wsgi [-] invalid
literal for int() with base 10: 'da8:2004:1000:202:116:160:90]'
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi Traceback (most
recent call last):
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/wsgi.py", line 238, in
__call__
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi result =
method(context, **params)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/token/controllers.py", line 94,
in authenticate
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi context,
auth)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/token/controllers.py", line
257, in _authenticate_local
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi username,
DEFAULT_DOMAIN_ID)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/identity/core.py", line 177, in
wrapper
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
f(self, *args, **kwargs)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/identity/core.py", line 337, in
get_user_by_name
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi driver =
self._select_identity_driver(domain_id)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/identity/core.py", line 280, in
_select_identity_driver
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi
self.get_domain(domain_id)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/identity/core.py", line 538, in
get_domain
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
self.assignment_api.get_domain(domain_id)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/cache/region.py", line 936, in
decorate
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi
should_cache_fn)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/cache/region.py", line 588, in
get_or_create
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi
async_creator) as value:
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py", line 158, in
__enter__
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
self._enter()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py", line 98, in
_enter
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi generated =
self._enter_create(createdtime)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/core/dogpile.py", line 149, in
_enter_create
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi created =
self.creator()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/cache/region.py", line 565, in
gen_value
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi created_value
= creator()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/dogpile/cache/region.py", line 932, in
creator
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
fn(*arg, **kw)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/assignment/core.py", line 262,
in get_domain
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
self.driver.get_domain(domain_id)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/assignment/backends/sql.py",
line 525, in get_domain
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi session =
self.get_session()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/sql/core.py", line 236,
in get_session
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi self._engine
= self.get_engine()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/sql/core.py", line 278,
in get_engine
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi engine =
new_engine()
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib/python2.6/site-packages/keystone/common/sql/core.py", line 251,
in new_engine
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi
connection_dict = sql.engine.url.make_url(CONF.sql.connection)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib64/python2.6/site-packages/sqlalchemy/engine/url.py", line 178,
in make_url
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
_parse_rfc1738_args(name_or_url)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib64/python2.6/site-packages/sqlalchemy/engine/url.py", line 216,
in _parse_rfc1738_args
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi return
URL(name, **components)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi File
"/usr/lib64/python2.6/site-packages/sqlalchemy/engine/url.py", line 56, in
__init__
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi self.port =
int(port)
2013-10-21 08:14:57.429 25606 TRACE keystone.common.wsgi ValueError:
invalid literal for int() with base 10: 'da8:2004:1000:202:116:160:90]'
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2851>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 20:53:55
|
#2850: cleanly upgrade the type of bindparam() with a null type
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: engine | 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:
r9caa92b96fef0b3e6d9d280407bc6a09
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2850#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 20:25:10
|
#2850: cleanly upgrade the type of bindparam() with a null type
------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: engine | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in progress |
------------------------------+-------------------------------
Comment (by zzzeek):
we're looking here to _clone the bindparam() so that we don't need to
mutate in place.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2850#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 20:24:43
|
#2850: cleanly upgrade the type of bindparam() with a null type
------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: engine | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in progress |
------------------------------+-------------------------------
Description changed by zzzeek:
Old description:
> {{{
> #!python
>
> bp = bindparam("somevalue")
> stmt = test_table.update().values(avalue=bp)
> compiled = stmt.compile()
> eq_(bp.type._type_affinity, types.NullType)
> eq_(compiled.binds['somevalue'].type._type_affinity,
> MyCustomType)
>
> }}}
New description:
{{{
#!python
bp = bindparam("somevalue")
stmt = test_table.update().values(avalue=bp)
compiled = stmt.compile()
eq_(bp.type._type_affinity, types.NullType)
eq_(compiled.binds['somevalue'].type._type_affinity, MyCustomType)
# additionally:
bp = bindparam("foo")
expr = column("foo", MyFoobarType) + bp
assert bp.type._type_affinity is types.NullType
assert expr.right.type._type_affinity is MyFoobarType
}}}
--
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2850#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 20:23:59
|
#2850: cleanly upgrade the type of bindparam() with a null type
-------------------------+------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: engine | Severity: major - 1-3 hours
Keywords: | Progress State: in progress
-------------------------+------------------------------------
{{{
#!python
bp = bindparam("somevalue")
stmt = test_table.update().values(avalue=bp)
compiled = stmt.compile()
eq_(bp.type._type_affinity, types.NullType)
eq_(compiled.binds['somevalue'].type._type_affinity, MyCustomType)
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2850>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 19:08:49
|
#2849: type_coerce refers to nonexistent __clause_expr__
-----------------------------------+-----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: highest | Milestone: 0.8.xx
Component: sql | Severity: trivial - <10 minutes
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in progress => completed/closed
Comment:
r622772b46999561ad2033c8d30ee9b1aff75951b 0.8
r56976624169af6d0d329b4834ee9caa7243573dc master
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2849#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 19:01:47
|
#2849: type_coerce refers to nonexistent __clause_expr__
---------------------+----------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.8.xx
Component: sql | Severity: trivial - <10 minutes
Keywords: | Progress State: in progress
---------------------+----------------------------------------
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2849>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 14:51:57
|
#2848: RowProxy don't get sorted as expected
------------------------------+----------------------------------
Reporter: pakal | Owner: zzzeek
Type: defect | Status: new
Priority: high | Milestone: 0.9.0
Component: engine | Severity: minor - half an hour
Resolution: | Keywords:
Progress State: needs tests |
------------------------------+----------------------------------
Changes (by zzzeek):
* priority: medium => high
* status_field: awaiting triage => needs tests
* component: cextensions => engine
* severity: no triage selected yet => minor - half an hour
* milestone: => 0.9.0
Comment:
patch:
{{{
#!diff
diff --git a/lib/sqlalchemy/engine/result.py
b/lib/sqlalchemy/engine/result.py
index 0e23165..93c7d3b 100644
--- a/lib/sqlalchemy/engine/result.py
+++ b/lib/sqlalchemy/engine/result.py
@@ -125,8 +125,11 @@ class RowProxy(BaseRowProxy):
__hash__ = None
+ def __lt__(self, other):
+ return tuple(self) < tuple(other)
+
def __eq__(self, other):
- return other is self or other == tuple(self)
+ return other is self or tuple(other) == tuple(self)
def __ne__(self, other):
return not self.__eq__(other)
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2848#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 13:01:10
|
#2848: RowProxy don't get sorted as expected
-------------------------+-----------------------------------------
Reporter: pakal | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone:
Component: cextensions | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
-------------------------+-----------------------------------------
If one uses raw queries like this:
res = list(session.execute("SELECT a,b FROM my_subscription"))
then we see (by printing) that res is [(0L, 13209L), (1L, 7057L), (2L,
410L), (10L, 3L), (6L, 10L)]
But these aren't tuples, so when we try to sort() that list (or use
sorted() on it), records just get weirdly mixed up.
I guess RowProxy objects should have the same behaviour as tuples when it
comes to sorting, or else they should display themselves as objects
instead of tuples, to avoid confusing unexperienced users.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2848>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 01:43:35
|
#2804: coerce_to_bool for where(), having(), etc.
------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by zzzeek):
* priority: medium => high
Comment:
starting out with an approach for short circuiting as well as treatment of
None in ticket_2804 branch, r1227103f0d1633a418a68b7269d7136f.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2804#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-21 01:41:05
|
#2739: disalllow None in filter()/where()/and_() ?
-----------------------------------+----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.9.0
Component: sql | Severity: minor - half an hour
Resolution: duplicate | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => duplicate
* status_field: not decided upon => completed/closed
Comment:
this is overlapped with #2804, will figure out how to include None
consistently.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2739#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-20 21:01:22
|
#2838: render_literal_bindparam() naively calls cached_bind_processor
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in queue => completed/closed
Comment:
r4663ec98b226a7d495846f0d89
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2838#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-20 20:33:02
|
#2842: The recipe "Storing/Using Enumerations" does not function in SQLite
-----------------------------------+------------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: utils | Severity: no triage selected yet
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Changes (by zzzeek):
* status: reopened => closed
* resolution: => fixed
* status_field: in progress => completed/closed
Comment:
r45ad8af3f97f2e6eee21ca3219827e82e3231cdf 0.8
r0b0764b62ba87bdec41d0fc86618f3779cb4e3f0 master
even with #2742, if the DeclEnum started implementing the upcoming
"process_literal_param()", the same failure would occur.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2842#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-10-20 20:22:05
|
#2842: The recipe "Storing/Using Enumerations" does not function in SQLite
------------------------------+------------------------------------
Reporter: rgg | Owner: zzzeek
Type: defect | Status: reopened
Priority: medium | Milestone: 0.8.xx
Component: utils | Severity: no triage selected yet
Resolution: | Keywords:
Progress State: in progress |
------------------------------+------------------------------------
Changes (by zzzeek):
* status: closed => reopened
* type: enhancement => defect
* priority: low => medium
* milestone: => 0.8.xx
* resolution: duplicate =>
* status_field: completed/closed => in progress
Comment:
this is resolved by #2742 but after closer inspection i think there's some
type mechanics that should be affected here too, the custom DeclEnum
should not be subject to the CHECK constraint that is receiving strings,
will coerce that.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2842#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
186 messages has been excluded from this view by a project administrator.
