Cool, thank you. Due to the bug I moved away from mapping a
selectable to do the job. But I'll keep in mind what you've said.
On Tue, Dec 7, 2010 at 9:01 PM, Michael Bayer mike...@zzzcomputing.com wrote:
its a bug, and theres a new ticket http://www.sqlalchemy.org/trac/ticket/1997
with a
On Dec 7, 6:06 pm, Michael Bayer mike...@zzzcomputing.com wrote:
I hadn't planned any future 0.5 releases, 0.7 is almost ready for betas.
What are the incompatibilities you have with 0.6 ?
One example is that Numeric(x,y) in oracle is now translated into
Python's Decimal in 0.6.x, was 'float'
On Dec 7, 6:06 pm, Michael Bayer mike...@zzzcomputing.com wrote:
I hadn't planned any future 0.5 releases, 0.7 is almost ready for betas.
What are the incompatibilities you have with 0.6 ?
Another difference to 0.5.x is that rolling back a fresh engine (or an
engine that has been rolled back)
On Dec 8, 2010, at 1:18 PM, Ralph Heinkel wrote:
On Dec 7, 6:06 pm, Michael Bayer mike...@zzzcomputing.com wrote:
I hadn't planned any future 0.5 releases, 0.7 is almost ready for betas.
What are the incompatibilities you have with 0.6 ?
One example is that Numeric(x,y) in oracle is now
On Dec 8, 2010, at 2:02 PM, Michael Bayer wrote:
engine.execute(select IEP from mytable where name='IP3').fetchone()
So here we're using text.In order for Numeric to be returned without loss
in accuracy, cx_oracle is configured now to return Decimal objects for
non-float
Hi Michael,
thanks for all your help and support. The Decimal problem is indeed
solved (the comma was the actual problem, not the fact that a numeric
is returned as Decimal). The other problem with rolling back a fresh
engine still persists, I've reopened ticket
