sqlalchemy-tickets Mailing List for SQLAlchemy (Page 95)
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-05-31 18:52:24
|
#960: implement MERGE
-------------------------+-------------------------------------------------
Reporter: jek | Owner: zzzeek
Type: | Status: new
enhancement | Milestone: 0.x.xx
Priority: low | Severity: refactor - over two days
Component: sql | Keywords: merge upsert replace on duplicate
Resolution: | key
Progress State: in |
queue |
-------------------------+-------------------------------------------------
Changes (by zzzeek):
* milestone: 0.9.0 => 0.x.xx
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/960#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-31 18:51:46
|
#2551: apparently INSERTs (and UPDATE, DELETE) can have CTEs in pg 9.1. plus
SELECT from INSERT, plus UPDATE in CTE.
------------------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: medium | Milestone: 0.9.xx
Component: postgres | Severity: very major - up to 2 days
Resolution: | Keywords:
Progress State: in queue |
------------------------------+---------------------------------------
Changes (by zzzeek):
* milestone: 0.9.0 => 0.9.xx
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2551#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-31 15:58:05
|
#2737: Unable to run update query with boolean filter expression (regression
0.8.0->0.8.1)
-----------------------------------+----------------------------------
Reporter: jgraham | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: orm | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* severity: no triage selected yet => minor - half an hour
* component: cextensions => orm
* milestone: => 0.8.xx
* resolution: => fixed
* status_field: awaiting triage => completed/closed
Comment:
its due to [ticket:2682]. This is fixed in rc6f54ae434b40f0ddfce (0.8)
r2cd1a43778d4dca08 (master)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2737#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-31 14:53:58
|
#2737: Unable to run update query with boolean filter expression (regression
0.8.0->0.8.1)
-------------------------+-----------------------------------------
Reporter: jgraham | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone:
Component: cextensions | Severity: no triage selected yet
Keywords: | Progress State: awaiting triage
-------------------------+-----------------------------------------
In 0.8.1 a query like
session.query(Test).filter(Test.a == False).update({"b":"b"})
fails, but it worked in 0.8.0. The failure seems to occur because
EvaluatorCompiler objects don't have a visit_false method. However I can't
see how this file, or expression.py have changed in a relevant way between
0.8.0 and 0.8.1.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2737>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-31 09:04:09
|
#2161: Py3k support for the C extension
-------------------------------+------------------------------------
Reporter: ged | Owner: pjenvey
Type: enhancement | Status: new
Priority: medium | Milestone: 0.8.xx
Component: cextensions | Severity: no triage selected yet
Resolution: | Keywords:
Progress State: needs review |
-------------------------------+------------------------------------
Changes (by pavel.brych):
* cc: pavel@… (added)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2161#comment:18>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-31 00:28:00
|
#2736: remove auto-aliasing from select_from()
-----------------------------------+----------------------------------
Reporter: zzzeek | 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
* status_field: in progress => completed/closed
Comment:
r04317bd5a887524956249565014c077afe41 in 0.9, r489312998f2faba63b3376651
has an upgrade path for 0.8
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2736#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-30 23:06:46
|
#2736: remove auto-aliasing from select_from()
--------------------+---------------------------------------
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
--------------------+---------------------------------------
The original use for select_from() is becoming obsolete. You can query
from a selectable and replace the primary entity using `aliased()`. The
behavior of `select_from()` where it applies the selectable as an alias to
the existing entities is unexpected behavior at this point as most users
are just trying to set up the FROM clause for a JOIN. The attached patch
changes this so that the old functionality is available via
`select_entity_from()`.
The `select_entity_from()` method can be added to 0.8 so that users have
an upgrade path into 0.9.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2736>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-29 23:35:26
|
#2735: postgresql HSTORE needs unicode support
-----------------------------------+----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.8.xx
Component: cextensions | Severity: minor - half an hour
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: in progress => completed/closed
Comment:
rf87c9d8167606da7f0bcd5d8e3f2f96be38c7100
r8fecf4b9cf439eca3926164f1bf6526060febfb9
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2735#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-29 22:07:45
|
#2735: postgresql HSTORE needs unicode support
-------------------------+---------------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.8.xx
Component: cextensions | Severity: minor - half an hour
Keywords: | Progress State: in progress
-------------------------+---------------------------------------
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2735>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-29 20:29:21
|
#2734: __eq__ operator appears to not be working correctly for decorated types
-----------------------------------+------------------------------------
Reporter: mcclurem | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone:
Component: declarative | Severity: no triage selected yet
Resolution: worksforme | Keywords: TypeDecorator
Progress State: completed/closed |
-----------------------------------+------------------------------------
Comment (by mcclurem):
Thanks so much for the explanation!
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2734#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-29 18:25:28
|
#2734: __eq__ operator appears to not be working correctly for decorated types
-----------------------------------+------------------------------------
Reporter: mcclurem | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone:
Component: declarative | Severity: no triage selected yet
Resolution: worksforme | Keywords: TypeDecorator
Progress State: completed/closed |
-----------------------------------+------------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => worksforme
* status_field: awaiting triage => completed/closed
Comment:
unfortunately this is a special use case that requires additional logic,
because SQLAlchemy coerces any "obj == None" into "obj IS NULL" - if you
turn on SQL echoing you will see this, and it occurs before the type is
consulted. Because it's a lexical change to the statement, there's not
really any way to move this consultation to a later point.
So the `__eq__()` (and probably `__ne__()` also) here must be overridden
specifically:
{{{
#!python
from sqlalchemy import *
from sqlalchemy.orm import *
from sqlalchemy.ext.declarative import declarative_base
class NullableString(TypeDecorator):
'''Turns None into the string "Null" and back in order to prevent
Null!=Null issues'''
impl = String
class comparator_factory(String.comparator_factory):
def __eq__(self, other):
if other is None:
return self.expr == "NONE"
else:
return String.comparator_factory.__eq__(self, other)
def process_bind_param(self, value, dialect):
return "NONE" if value is None else value
def process_result_value(self, value, dialect):
return None if value == "NONE" else value
Base = declarative_base()
class A(Base):
__tablename__ = 'a'
id = Column(Integer, primary_key=True)
value = Column(NullableString, nullable=False)
e = create_engine("sqlite://", echo=True)
Base.metadata.create_all(e)
sess = Session(e)
sess.add_all([A(value='x'), A(value=None)])
sess.commit()
assert sess.execute("select id, value from a order by id").fetchall() ==
[(1, 'x'), (2, 'NONE')]
assert sess.query(A).filter(A.value == 'x').one().id == 1
assert sess.query(A).filter(A.value == None).one().id == 2
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2734#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-29 15:26:14
|
#2734: __eq__ operator appears to not be working correctly for decorated types
---------------------------+-----------------------------------------
Reporter: mcclurem | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone:
Component: declarative | Severity: no triage selected yet
Keywords: TypeDecorator | Progress State: awaiting triage
---------------------------+-----------------------------------------
So from the documentation it makes it appear that by defining
`process_bind_param` and `process_result_value` I should have all the
workings to transparently perform a translation. However the == operator
doesn't perform the translation before sending the query to the db.
Here's my example:
{{{
#!div style="font-size: 80%"
{{{#!python
class NullableString(TypeDecorator):
'''Turns None into the string "Null" and back in order to prevent
Null!=Null issues'''
impl = String
def process_bind_param(self, value, dialect):
return "NONE" if value is None else value
def process_result_value(self, value, dialect):
return None if value == "NONE" else value
}}}
}}}
If I have a class `SomeType` and I perform the following:
{{{
#!div style="font-size: 80%"
{{{#!python
session.query(SomeType).filter(SomeType.nullableStringCol ==
None).all()
}}}
}}}
I get no results but if I do:
{{{
#!div style="font-size: 80%"
{{{#!python
session.query(SomeType).filter(SomeType.nullableStringCol ==
"NONE").all()
}}}
}}}
I get my results.
Now I can get around this by declaring the instance of the
`NullableString` to use a custom comparator in `SomeType` but that seems
like a broken paradigm because that comparison behavior should be captive
within my new type.
Am I misunderstanding the mechanism for the comparison?
I apologize if this isn't a bug but it seems like it's broken (the example
of typedecorators in the docs would presumably suffer the same problem
when comparing unicode strings)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2734>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-28 01:45:18
|
#1068: render 'SELECT foo() AS x .. ORDER BY x' by default
------------------------------+-------------------------------
Reporter: jek | Owner: anyone
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: sql | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in progress |
------------------------------+-------------------------------
Changes (by zzzeek):
* priority: medium => high
* milestone: blue sky => 0.8.xx
* status_field: needs a volunteer => in progress
Comment:
the branch at
http://www.sqlalchemy.org/trac/log/?rev=ff399ac75074916045410cedae72489cb60e8b50
has this working. Oracle seems OK with it, at least 10G. The branch
includes a compliance test in the dialect suite.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1068#comment:15>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 22:29:02
|
#1457: Self-referential relation fails silently if an entity references itself
-----------------------------------+----------------------------------
Reporter: ants | Owner: zzzeek
Type: defect | Status: closed
Priority: medium | Milestone: 0.x.xx
Component: orm | Severity: minor - half an hour
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+----------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => worksforme
* status_field: awaiting triage => completed/closed
Comment:
this test case fails appropriately since the unit of work refactor in 0.6.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/1457#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 22:22:57
|
#2416: Support batch inserts with multiple values() calls
-----------------------------------+-------------------------------
Reporter: schmichael | 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:
this was implemented six months ago as #2623.
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2416#comment:7>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 22:17:35
|
#2733: using backref raises AttributeError when querying column-based entities
[declarative extension]
-----------------------------------+------------------------------------
Reporter: andrija | Owner: zzzeek
Type: defect | Status: closed
Priority: lowest | Milestone:
Component: declarative | Severity: no triage selected yet
Resolution: worksforme | Keywords:
Progress State: completed/closed |
-----------------------------------+------------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => worksforme
* status_field: awaiting triage => completed/closed
Comment:
this is just mappers not getting configured, and your relationship is
declared as a backref. you can refer to columns before this occurs for
mapping purposes.
add
{{{
from sqlalchemy.orm import configure_mappers
configure_mappers()
}}}
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2733#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 22:13:12
|
#2289: disallow Session /state alteration when flush context actually executing ?
-----------------------------------+-------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: closed
Priority: medium | Milestone: blue sky
Component: orm | Severity: major - 1-3 hours
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-------------------------------
Changes (by zzzeek):
* status: new => closed
* resolution: => fixed
* status_field: on hold => completed/closed
Comment:
this is done some months ago as a warning, 1c3e3225
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2289#comment:2>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 22:07:51
|
#2072: add c.execution_options(isolation_level='AUTOCOMMIT') for psycopg2 dialect
------------------------------+----------------------------------
Reporter: zzzeek | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: minor - half an hour
Resolution: | Keywords:
Progress State: in queue |
------------------------------+----------------------------------
Changes (by zzzeek):
* priority: medium => high
* milestone: 0.x.xx => 0.8.xx
Old description:
New description:
some PG functions need this
--
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2072#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 16:56:27
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by foobar):
* cc: foobar@… (removed)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:10>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 16:56:09
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by foobar):
* cc: foobar@… (added)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:9>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 16:55:53
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by foobar):
* cc: foobar@… (removed)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:8>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 16:55:37
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by foobar):
* cc: foobar@… (added)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:7>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 15:17:03
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by zzzeek):
* cc: foobar (removed)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:6>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-27 15:16:28
|
#2581: PostgreSQL-9.2 JSON datatype
------------------------------+-------------------------------
Reporter: plaes | Owner: zzzeek
Type: enhancement | Status: new
Priority: high | Milestone: 0.8.xx
Component: postgres | Severity: major - 1-3 hours
Resolution: | Keywords:
Progress State: in queue |
------------------------------+-------------------------------
Changes (by zzzeek):
* cc: foobar (added)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2581#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
|
From: sqlalchemy <mi...@zz...> - 2013-05-26 14:25:32
|
#2717: AbstractConcreteBase class provides incorrect example
-----------------------------------+-----------------------------------
Reporter: markhildreth | Owner: diana
Type: defect | Status: closed
Priority: low | Milestone: 0.8.xx
Component: documentation | Severity: trivial - <10 minutes
Resolution: fixed | Keywords:
Progress State: completed/closed |
-----------------------------------+-----------------------------------
Changes (by diana):
* status: new => closed
* resolution: => fixed
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2717#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|
186 messages has been excluded from this view by a project administrator.
