sqlalchemy-tickets Mailing List for SQLAlchemy (Page 64)
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...> - 2014-01-01 21:31:50
|
#2901: unicode backrefs broken on python 2
-------------------------------+----------------------------------
Reporter: gazpachoking | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: minor - half an hour
Resolution: | Keywords:
Progress State: in queue |
-------------------------------+----------------------------------
Changes (by zzzeek):
* priority: medium => highest
* severity: no triage selected yet => minor - half an hour
* status_field: awaiting triage => in queue
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2901#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 21:31:32
|
#2901: unicode backrefs broken on python 2
----------------------------------+------------------------------------
Reporter: gazpachoking | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.9.xx
Component: orm | Severity: no triage selected yet
Resolution: | Keywords:
Progress State: awaiting triage |
----------------------------------+------------------------------------
Comment (by zzzeek):
OK that should probably be "isinstance(self.backref, util.string_types),
need to take a look.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2901#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 21:30:54
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
I'd like to shore up the "how do we tell what kind of attribute this is"
test a bit better, just checking for different key is not strong enough.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:6>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 21:30:20
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
i think just having decalrative turn them into synonyms is the most
straightforward route, otherwise we really can't be too smart about what's
going on, e.g. in the original case where !FooChild has "parent =
Child.foo" inline:
{{{
#!diff
diff --git a/lib/sqlalchemy/ext/declarative/base.py
b/lib/sqlalchemy/ext/declarative/base.py
index f7668a5..a571d07 100644
--- a/lib/sqlalchemy/ext/declarative/base.py
+++ b/lib/sqlalchemy/ext/declarative/base.py
@@ -6,9 +6,10 @@
"""Internal implementation for declarative."""
from ...schema import Table, Column
-from ...orm import mapper, class_mapper
+from ...orm import mapper, class_mapper, synonym
from ...orm.interfaces import MapperProperty
from ...orm.properties import ColumnProperty, CompositeProperty
+from ...orm.attributes import QueryableAttribute
from ...orm.base import _is_mapped_class
from ... import util, exc
from ...sql import expression
@@ -148,6 +149,15 @@ def _as_declarative(cls, classname, dict_):
if isinstance(value, declarative_props):
value = getattr(cls, k)
+ elif isinstance(value, QueryableAttribute) and \
+ value.class_ is not cls and \
+ value.key != k:
+ # detect a QueryableAttribute that's already mapped being
+ # assigned elsewhere in userland, turn into a synonym()
+ value = synonym(value.key)
+ setattr(cls, k, value)
+
+
if (isinstance(value, tuple) and len(value) == 1 and
isinstance(value[0], (Column, MapperProperty))):
util.warn("Ignoring declarative-like tuple value of attribute
"
@@ -397,6 +407,7 @@ def _add_attribute(cls, key, value):
adds it to the Mapper, adds a column to the mapped Table, etc.
"""
+
if '__mapper__' in cls.__dict__:
if isinstance(value, Column):
_undefer_column_name(key, value)
@@ -413,6 +424,11 @@ def _add_attribute(cls, key, value):
key,
clsregistry._deferred_relationship(cls, value)
)
+ elif isinstance(value, QueryableAttribute) and value.key != key:
+ # detect a QueryableAttribute that's already mapped being
+ # assigned elsewhere in userland, turn into a synonym()
+ value = synonym(value.key)
+ type.__setattr__(cls, key, value)
else:
type.__setattr__(cls, key, value)
else:
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 21:03:32
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
looking into the backref issue specifically, it is related to inheritance
and the fact that Child.foo doesn't belong on `FooChild.foo`:
{{{
# breaks
FooChild.parent = Child.foo
# works
#FooChild.parent = FooChild.foo
FooChild(parent=Foo())
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 19:44:48
|
#2901: unicode backrefs broken on python 2
----------------------------------+------------------------------------
Reporter: gazpachoking | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.9.xx
Component: orm | Severity: no triage selected yet
Resolution: | Keywords:
Progress State: awaiting triage |
----------------------------------+------------------------------------
Comment (by gazpachoking):
This is an issue when using `from __future__ import unicode_literals`,
don't think it's really a problem otherwise.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2901#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 18:45:09
|
#2901: unicode backrefs broken on python 2
--------------------------+-----------------------------------------
Reporter: gazpachoking | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.9.xx
Component: orm | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
--------------------------+-----------------------------------------
It seems that backrefs can no longer be unicode strings on 0.9 in python
2. When they are, the following problem occurs, due to the type check `if
isinstance(self.backref, str):`:
{{{
File "...\sqlalchemy\orm\relationships.py", line 1566, in
_generate_backref
backref_key, kwargs = self.backref
ValueError: too many values to unpack
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2901>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 18:20:19
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
so, if we can just have an `InstrumentedAttribute` referred to by many
keys, what does `synonym()` really get us if you aren't using descriptor
overrides? obviously we have to fix the recursion catch in backrefs
here. but should we try to build in "mirror the instrumented attribute"
behavior at the declared level also, then this means we're revising #2828.
#2828 inconsistently doesn't seem to apply to relationships either? seems
like we might have screwed up on this one.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 18:17:01
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Comment (by zzzeek):
OK figuring out what's happening here, and also considering what exactly
is `synonym()` for really, if we can just do this? What is basically the
pattern here is that the `InstrumentedAttribute` is just assigned a second
time somewhere else. declarative isn't really getting involved here other
than just setting the attribute. same pattern in classical:
{{{
#!python
from sqlalchemy import Column, Integer, ForeignKey, Table, MetaData
from sqlalchemy.orm import relationship, backref, mapper
m = MetaData()
child = Table('child', m,
Column('id', Integer, primary_key=True),
Column('foo_id', ForeignKey('foo.id'))
)
foo = Table('foo', m,
Column('id', Integer, primary_key=True)
)
class Child(object):
pass
class Foo(object):
pass
class FooChild(Child):
pass
mapper(Child, child, properties={
'foo': relationship(Foo, backref=backref('children'))
})
mapper(Foo, foo)
mapper(FooChild, None, inherits=Child)
Child.parent = Child.foo
Child.brap = Child.foo_id
fc = FooChild()
fc.parent = Foo()
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 17:04:05
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------------+-------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.xx
Component: orm | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-------------------------------
Changes (by zzzeek):
* priority: medium => highest
* status_field: awaiting triage => in queue
* severity: no triage selected yet => major - 1-3 hours
* milestone: => 0.9.xx
Comment:
mmm OK, well use a synonym for that now, the thing you're doing there, if
it works in 0.8, works entirely by accident:
{{{
#!python
class FooChild(Child):
parent = synonym("foo")
}}}
the way that is now, the relationship() is probably being set up
incorrectly and when I look into it, i might prefer that pattern just
raise an exception, or make an implicit synonym, not really sure.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2014-01-01 16:31:20
|
#2900: relationship aliased on subclass causes infinite recursion
---------------------+-----------------------------------------
Reporter: scraper | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone:
Component: orm | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
---------------------+-----------------------------------------
Having additional names for a relationship in a subclass works with
sqlalchemy <= 0.8.4
With 0.9.0 setting the attribute as seen below gives '''RuntimeError:
maximum recursion depth exceeded'''
{{{
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy import Column, Integer, ForeignKey
from sqlalchemy.orm import relationship, backref
Base = declarative_base()
class Child(Base):
__tablename__ = 'child'
id = Column(Integer, primary_key=True)
foo_id = Column(Integer, ForeignKey('foo.id'))
foo = relationship('Foo', backref=backref('children'))
class FooChild(Child):
parent = Child.foo
class Foo(Base):
__tablename__ = 'foo'
id = Column(Integer, primary_key=True)
FooChild(parent=Foo())
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2900>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 21:39:01
|
#2899: regression in CAST behavior due to type_coerce enhancement
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: highest | 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 progress => completed/closed
Comment:
rcac7320eeb16e62f347dbf009
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2899#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 20:34:27
|
#2899: regression in CAST behavior due to type_coerce enhancement
---------------------+------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: highest | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Keywords: | Progress State: in progress
---------------------+------------------------------------
works in 0.8, fails in 0.9:
{{{
from sqlalchemy import *
class MyType(TypeDecorator):
impl = Unicode
type_ = MyType()
value = cast(literal("hi", type_), Unicode)
assert value.clause.type is type_ # <- becomes unicode, MyType is lost
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2899>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:31:44
|
#2448: Informix backend hasn't been tested since at least 0.5
-----------------------------------+-------------------------------
Reporter: Crooksey | Owner: zzzeek
Type: defect | Status: closed
Priority: high | Milestone: 0.x.xx
Component: informix | Severity: major - 1-3 hours
Resolution: wontfix | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => wontfix
* status_field: needs a volunteer => completed/closed
Comment:
see also #1650 - informix is moved out and superseded by
http://code.google.com/p/ibm-db/.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2448#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:29:55
|
#2172: mssql+pymssql does not recover from connection failure due to timeout or
TCP closed
-----------------------------------+----------------------------------
Reporter: guest | Owner:
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: mssql | Severity: minor - half an hour
Resolution: fixed | Keywords: pymssql
Progress State: completed/closed |
-----------------------------------+----------------------------------
Comment (by zzzeek):
"net lib reset by peer" in 0.8 is r4211207abfd96
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2172#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:28:42
|
#2172: mssql+pymssql does not recover from connection failure due to timeout or
TCP closed
-----------------------------------+----------------------------------
Reporter: guest | Owner:
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: mssql | Severity: minor - half an hour
Resolution: fixed | Keywords: pymssql
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* status_field: awaiting triage => completed/closed
* resolution: => fixed
* milestone: 0.x.xx => 0.8.xx
Comment:
we should have committed this patch a long time ago, however both of these
messages have ultimately been added by a production shop, see
r3147ca30401aa and reefa4b68f5dce.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2172#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:23:25
|
#2877: text as from
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: closed
Priority: high | Milestone: 0.9.0
Component: sql | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Comment (by zzzeek):
also see #2478 for the original trac ticket I couldn't find.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2877#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:23:11
|
#2478: Better support for raw SQL select statements
-----------------------------------+-------------------------------
Reporter: andreypopp | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: 0.x.xx
Component: sql | Severity: major - 1-3 hours
Resolution: duplicate | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => duplicate
* status_field: in queue => completed/closed
Comment:
I totally could not find this ticket a few weeks ago when I instead
implemented this as #2877. See
http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html#new-
text-capabilities which implements these and more features. The types are
optional, but overall the typing information in SQLAlchemy is important
for the cases of both expression behavior (e.g. an ARRAY type has [] for
example, others don't, the "+" operator in a string does concatenation,
etc.) as well as Python-level coersion (e.g. you might want to receive
Decimal or floating point numbers, unicode, booleans for ints etc).
anyway, resolved as #2877.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2478#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:17:32
|
Batch modification to #1384, #2119 by zzzeek: status_field to completed/closed Action: resolve Comment: "alternate" dialects like these can now be tackled as projects external to SQLAlchemy itself. -- Tickets URL: <http://www.sqlalchemy.org/trac/query?id=1384%2C2119> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:15:34
|
#1650: test Informix dialect against an actual Informix database
-----------------------------------+-------------------------------
Reporter: guest | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: blue sky
Component: informix | Severity: major - 1-3 hours
Resolution: wontfix | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => wontfix
* status_field: needs a volunteer => completed/closed
Comment:
informix is moved out to an experimental dialect, and production level
informix support is now available via http://code.google.com/p/ibm-db/.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1650#comment:6>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:13:02
|
Batch modification to #2609 by zzzeek: milestone to 0.x.xx -- Tickets URL: <http://www.sqlalchemy.org/trac/query?id=2609> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |
|
From: sqlalchemy <mi...@zz...> - 2013-12-28 19:11:45
|
Batch modification to #2694, #2795, #2642 by zzzeek: milestone to 0.x.xx -- Tickets URL: <http://www.sqlalchemy.org/trac/query?id=2694%2C2795%2C2642> sqlalchemy <http://www.sqlalchemy.org/> The Database Toolkit for Python |
|
From: sqlalchemy <mi...@zz...> - 2013-12-27 23:28:43
|
#2687: .cast() as an operator
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: 0.9.0
Component: postgres | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* component: sql => postgres
* milestone: 0.8.xx => 0.9.0
* resolution: => fixed
* status_field: in queue => completed/closed
Comment:
this is pretty specific to the new JSON type for now.
r2104d0ba2d612a26d36
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2687#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-27 22:11:43
|
#2828: emit warning when Column is assigned directly to multiple names
-----------------------------------+----------------------------------
Reporter: jerryji | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.9.0
Component: declarative | Severity: minor - half an hour
Resolution: fixed | Keywords: column_property
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* status_field: needs tests => completed/closed
* resolution: => fixed
* severity: major - 1-3 hours => minor - half an hour
* milestone: 0.8.xx => 0.9.0
Comment:
more complete version detects any kind of name collision:
rde786a4208e621229769a8fb1f876f
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2828#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-12-27 21:40:51
|
#2898: get_table_names should not return views
-----------------------------------+-------------------------------
Reporter: treeve | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.9.0
Component: firebird | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* status_field: needs questions answered => completed/closed
* resolution: => fixed
* milestone: 0.8.xx => 0.9.0
Comment:
rf50c670e47bb562ee23b52f in 0.9
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2898#comment:6>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
186 messages has been excluded from this view by a project administrator.
