Re: [sqlalchemy] Pyodbc.Connection has no attribute 'dbms_ver'?

Try to use ibm_db_sa 0.3.2 instead, apparently you are using the previous version. dbms_ver is a feature specific of native ibm_db version of which not available in pyodbc. https://pypi.python.org/pypi/ibm_db_sa/0.3.2 Salam, -Jaimy. On Feb 12, 2016 22:05, "Alex Hall"

Re: [sqlalchemy] Connecting to AS400 with SQLAlchemy fails

Connecting to AS400 from native ibm_db_dbi driver would need db2 connect which is a separated product from IBM. Use the ibm_db_sa pyodbc driver instead, or jdbc (jython) if you don't have db2 connect installed on your machine. Salam, -Jaimy On Feb 11, 2016 01:50, "Alex Hall"

Re: [sqlalchemy] Latest SA version which support Jython

; > > On 01/18/2016 09:23 PM, Jaimy Azle wrote: > > Hi all, > > > > I know jython support was dropped from current version of sqlalchemy, > > but here I'm stuck to keep use jython in our application due to the Java > > based technology infrastructures used. > >

[sqlalchemy] Latest SA version which support Jython

Hi all, I know jython support was dropped from current version of sqlalchemy, but here I'm stuck to keep use jython in our application due to the Java based technology infrastructures used. In the past I did cancel upgrade from 0.7.2 since 0.7.3 and later introduce delayed import mechanism

Re: [sqlalchemy] Writing simple dialect for iSeries + pyodbc in order to use engine.execute for sql statements.

Actually the ibm_db_sa support several methods to connect to iSeries; natively through ibm_db, pyodbc, or jdbc (with jython). On Jun 8, 2014 8:53 AM, Cory Lutton cory.lut...@gmail.com wrote: Thanks for such a quick reply. Great to hear that I am starting out on the right path with building a

Re: [sqlalchemy] Writing simple dialect for iSeries + pyodbc in order to use engine.execute for sql statements.

AM UTC-7, Jaimy Azle wrote: Actually the ibm_db_sa support several methods to connect to iSeries; natively through ibm_db, pyodbc, or jdbc (with jython). On Jun 8, 2014 8:53 AM, Cory Lutton cory@gmail.com wrote: Thanks for such a quick reply. Great to hear that I am starting out

Re: [sqlalchemy] Performance degradation after few hours running

test_dict_creation_mode1 0.150935604 0.42927071 0.961422087 test_dict_instance_getattr_instance_dict 0.267798221 0.506267055 1.389867345 I will try to make a deeper observation on this. -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring

[sqlalchemy] Performance degradation after few hours running

stack used: * JDK 1.6 * Jetty 6 * Jython 2.5.3 * IBM DB2 * SQLA 0.7.8 * SQL Elixir 0.7.1 -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1 for spreading FUD about perl. It's absolutely not dead.” – Daenyth “+1 + -1 = 0, then, is perl

[sqlalchemy] Please enhance SA support on loading dialect from entry points

@hostname:port/database -- Salam, -Jaimy Azle -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com

Re: [sqlalchemy] Please enhance SA support on loading dialect from entry points

in entry_points the configuration would be: [sqlalchemy.dialects] ibm_db_sa = ibm_db_sa.base:dialect ibm_db_sa.pyodbc = ibm_db_sa.pyodbc:dialect ibm_db_sa.zxjdbc = ibm_db_sa.zxjdbc:dialect -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1

[sqlalchemy] ORM Event

, -Jaimy Azle code snippet - from sqlalchemy import create_engine, event from sqlalchemy import Column, Integer, String from sqlalchemy.orm import sessionmaker, mapper from sqlalchemy.ext.declarative import declarative_base Base = declarative_base() engine = create_engine('sqlite

Re: [sqlalchemy] ORM Event

operation? for this case I need to validate each instance after they were inserted or before they were deleted from a persistence storage and adjust some rows from another table. -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1

Re: [sqlalchemy] ORM Event

indicates two inserts for Detail, one insert for Master, as expected: Ups i believe it was my bad, combining two cases in one test. Anyway, I got it, thanks.. :) -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1 for spreading FUD about

Re: [sqlalchemy] Cursor objects in Sessions

/browse_thread/thread/95e3a4ffe806a4bf -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1 for spreading FUD about perl. It's absolutely not dead.” – Daenyth “+1 + -1 = 0, then, is perl a zombie?” – joaquin -- http://stackoverflow.com

Re: [sqlalchemy] Discarded overflow connection object object does not automatically close DB socket connection in Jython

then it is checked out and refreshed/recycled. I think i would need to extend QueuePool, and Queue by adding a functionality to monitor those idle time connection and dispose it from the pool when maximum idle time reached. -- Salam, -Jaimy Azle - http://jaim.log.web.id -- You received

Re: [sqlalchemy] Discarded overflow connection object object does not automatically close DB socket connection in Jython

, -Jaimy Azle -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group

[sqlalchemy] Discarded overflow connection object object does not automatically close DB socket connection in Jython

._overflow -= 1 conn.close() else: self._overflow_lock.acquire() try: self._overflow -= 1 conn.close() finally: self._overflow_lock.release() -- Salam, -Jaimy Azle

Re: [sqlalchemy] Howto identify connection which has not been returned back to the pool?

/interfaces.html#sqlalchemy.interfaces.PoolListener Ok, Thanks for pointing, I will look into this. -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1 for spreading FUD about perl. It's absolutely not dead.” – Daenyth “+1 + -1 = 0

Re: [sqlalchemy] Howto identify connection which has not been returned back to the pool?

in the pool were also listed there. -- Salam, -Jaimy Azle “+1 for stating fact: Perl is dead. Please don't bring it back” – Matt Joiner “-1 for spreading FUD about perl. It's absolutely not dead.” – Daenyth “+1 + -1 = 0, then, is perl a zombie?” – joaquin -- http://stackoverflow.com

[sqlalchemy] Howto identify connection which has not been returned back to the pool?

...0x2:Connection PyConnection object at 0xc70 ... checked out from pool sqlalchemy.pool.QueuePool.0x...0x2:Connection PyConnection object at 0xc70 ... being returned to pool -- Salam, -Jaimy Azle -- You received this message because you are subscribed to the Google Groups sqlalchemy group

[sqlalchemy] MS SQL wrapper for pymssql DBAPI broken in 0.5.0

: obj.CMSTAUDT = 20090103 session.update(obj) session.commit() session.close() except: session.rollback() raise if __name__ == '__main__': setUp_dbconn() unittest.main() -- Salam, -Jaimy Azle Great new ideas usually come from very small teams... don't give up so

[sqlalchemy] Re: How to identify a transaction that has already begun

be used? -- Salam, -Jaimy Azle Great new ideas usually come from very small teams... don't give up so easily. -- John Kaster --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post

[sqlalchemy] Re: mssql wrapper for numeric Datatype.

if not isinstance(value, float) and value._exp -6: AttributeError: 'int' object has no attribute '_exp' -- Salam, -Jaimy Azle Great new ideas usually come from very small teams... don't give up so easily. -- John Kaster --~--~-~--~~~---~--~~ You received

[sqlalchemy] How to identify a transaction that has already begun

to identify whether the transaction has already begun to avoid exception? -- Salam, -Jaimy Azle Great new ideas usually come from very small teams... don't give up so easily. -- John Kaster --~--~-~--~~~---~--~~ You received this message because you

[sqlalchemy] Re: DBMS

interface problem here. Back when I made my Master of Informatics I learned a whole lot about DBMSs. probably virus? -- Salam, -Jaimy Azle Train yourselft to let go of everything you fear to loose. -- Master Yoda --~--~-~--~~~---~--~~ You received

[sqlalchemy] SQLAlchemy change Decimal type operation behaviour

Hi, I have a problem on using Decimal type along with SQLAlchemy, the decimal value could not be used for any computation after querying something with SQLAlchemy object. This is reproducable in my machine: import decimal from tbl import SBCITM pval = decimal.Decimal(decimal.Decimal('0.999') *

[sqlalchemy] Re: SQLAlchemy change Decimal type operation behaviour

to write some similar test case soon as this is really reproducable in my machine. -- Salam, -Jaimy Azle Train yourselft to let go of everything you fear to loose. -- Master Yoda --~--~-~--~~~---~--~~ You received this message because you are subscribed

[sqlalchemy] Re: SQLAlchemy change Decimal type operation behaviour

On Monday, January 14, 2008, 8:46:15 AM, Jaimy Azle wrote: I will try to write some similar test case soon as this is really reproducable in my machine. Sadly, ...and strange. I can reproduce it on every part of my project source, but not on a simple test-case. Yet the problem is still

[sqlalchemy] Re: SQLAlchemy change Decimal type operation behaviour

, -Jaimy Azle Train yourselft to let go of everything you fear to loose. -- Master Yoda --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy