Chris Withers wrote:
Michael Bayer wrote:
Chris Withers wrote:
Michael Bayer wrote:
Has anyone (hi, list, talking to you too!) already done a custom type
for this specific problem?
people do custom types for all sorts of things. In the case of the
Decimal here I'd likely subclass
Michael Bayer wrote:
the whole ugly discussion is at http://www.sqlalchemy.org/trac/ticket/1759
Speshul...
*sigh*
I'm glad I don't have your responsibilities ;-)
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
- http://www.simplistix.co.uk
--
You
Michael Bayer wrote:
Has anyone (hi, list, talking to you too!) already done a custom type
for this specific problem?
people do custom types for all sorts of things. In the case of the
Decimal here I'd likely subclass sqlalchemy.databases.sqlite.SLNumeric
which should ensure that your own
Chris Withers wrote:
Michael Bayer wrote:
Has anyone (hi, list, talking to you too!) already done a custom type
for this specific problem?
people do custom types for all sorts of things. In the case of the
Decimal here I'd likely subclass sqlalchemy.databases.sqlite.SLNumeric
which should
Hi Michael,
Thanks for this, I thought I asked this separately but I can't find the
mail now...
How would you recommend I work this now in 0.5.8 until I can move to
0.6.0? (which will take some months :-S)
I seem to remember you suggesting a custom type. Where can I find
examples of those
Chris Withers wrote:
Hi Michael,
Thanks for this, I thought I asked this separately but I can't find the
mail now...
How would you recommend I work this now in 0.5.8 until I can move to
0.6.0? (which will take some months :-S)
I seem to remember you suggesting a custom type. Where can I
Michael Bayer wrote:
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The
SQLite date types don't expect this to be turned on. That is a
handy feature which I'm not sure was available in such a simple form
when I first wrote against the pysqlite dialect in Python 2.3.
Indeed,
On Feb 26, 2010, at 8:50 AM, Chris Withers wrote:
Michael Bayer wrote:
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The
SQLite date types don't expect this to be turned on. That is a
handy feature which I'm not sure was available in such a simple form
when I first wrote
On Feb 26, 2010, at 8:50 AM, Chris Withers wrote:
Michael Bayer wrote:
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The
SQLite date types don't expect this to be turned on. That is a
handy feature which I'm not sure was available in such a simple form
when I first wrote
ticket #1717
On Feb 26, 2010, at 10:28 AM, Michael Bayer wrote:
On Feb 26, 2010, at 8:50 AM, Chris Withers wrote:
Michael Bayer wrote:
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The
SQLite date types don't expect this to be turned on. That is a
handy feature which
fixed in r6859. please don't use those crappy pysqlite converters.
On Feb 26, 2010, at 8:50 AM, Chris Withers wrote:
from sqlalchemy import create_engine
from sqlalchemy.orm import sessionmaker
from sqlalchemy.orm.session import Session
from sqlalchemy.ext.declarative import
Michael Bayer wrote:
On Feb 26, 2010, at 8:50 AM, Chris Withers wrote:
Michael Bayer wrote:
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The
SQLite date types don't expect this to be turned on. That is a
handy feature which I'm not sure was available in such a simple form
Hi All,
With SA 0.5.8 on Python 2.5, the attached test_with_default blows up with:
Traceback (most recent call last):
File test_default_arg_sqlite.py, line 46, in test_with_default
peterb2 = session.query(PersonWITH).filter_by(name='PeterB').first()
File
not sure if this is obvious, its the sqlite3.PARSE_DECLTYPES. The SQLite date
types don't expect this to be turned on. That is a handy feature which I'm
not sure was available in such a simple form when I first wrote against the
pysqlite dialect in Python 2.3.
A workaround is to use a
14 matches
Mail list logo
