On Mon, Feb 6, 2012 at 10:59 AM, Michael Bayer wrote:
>
> Attached is a patch that allows "coerce_to_decimal" to be passed to
> create_engine() and will disable the output handling if passed as False. Do
> you want to give it a try, I can commit it for 0.7.6 if it does the trick.
It passed my
Thanks for the quick reply. A few follow-up questions...
On Sun, Feb 5, 2012 at 9:03 PM, Michael Bayer wrote:
> My first suggestion would be to just use cdecimal. That way performance
> would not be an issue - I patch it in at program start time using the example
> at
> http://docs.sqlalchem
How do I set up an engine so that Oracle Number fields are not
converted to Decimal?
I'm dealing with a bunch of code with hand-rolled SQL query strings,
and as the first step was going to use connections from SqlAlchemy's
connection pool, as I change the queries one-by-one. The only problem
is t
On Tue, Dec 13, 2011 at 11:20 AM, Michael Bayer
wrote:
> As far as how you'd make your own Oracle "upsert" thing for now, you'd use
> the @compiles system which is documented at:
> http://www.sqlalchemy.org/docs/core/compiler.html . We do sometimes put up
> recipes for these things either on
I'm trying to convert our code to use the SqlAlchemy Expression
Language instead of manually building the sql statements strings (plus
we should be able to easily switch to sqlite for unit-testing
purposes). I'm worried about a few statement, in particular this
Oracle upsert command:
sql = ""
