[sqlalchemy] sequence in sqlalchemy

2020-07-02 Thread Anoop Thiparala
id = db.Column(db.Integer, Sequence('patients_seq', start=1, increment=1) , primary_key=True) any reason why this is not working with sqlite3 -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE:

Re: [sqlalchemy] SQLAlchemy Memory

2013-01-14 Thread Anoop K
the 0.7.9 C extension case mentioned) ? Thanks for the excellent support. Anoop On Monday, January 14, 2013 8:04:03 PM UTC+5:30, Michael Bayer wrote: I'm not seeing that. Script attached again, it runs in a fixed loop. Memory under top is not moving. So need to know: - exact SQLAlchemy

Re: [sqlalchemy] SQLAlchemy Memory

2013-01-13 Thread Anoop K
I tried memory tests by *reusing engine *and memory is steady. I feel some memory is held up even after the release of engine. On Sunday, 13 January 2013 12:21:10 UTC+5:30, Anoop K wrote: gc.collect() was not called in the last sample. Here is one where gc.collect() is also called class

Re: [sqlalchemy] SQLAlchemy Memory

2013-01-13 Thread Anoop K
the caching result in this high numbers ?? Thanks Anoop On Monday, 14 January 2013 03:50:35 UTC+5:30, Michael Bayer wrote: I think if you truly want to measure unlimited memory growth, you need to watch the total memory of the process, under load, over time.It will grow to a certain

[sqlalchemy] SQLAlchemy Memory

2013-01-12 Thread Anoop K
'sqlalchemy.types.Integer': last:52 curr:59 diff:7 type 'function': last:8077 curr:8392 diff:315 Thanks Anoop * * -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/gESaFAd9DHkJ

Re: [sqlalchemy] SQLAlchemy Memory

2013-01-12 Thread Anoop K
On Sunday, 13 January 2013 11:45:11 UTC+5:30, Michael Bayer wrote: On Jan 13, 2013, at 12:40 AM, Anoop K wrote: Hi, I had POSTed a question( https://groups.google.com/forum/?fromgroups=#!topic/sqlalchemy/vCjrGE9zYwQ ) related to session/engine cleanup. After fixing the engine cleanup

[sqlalchemy] SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
It seems engine created using *create_engine* is not freed after cleanup of a session. Object graph indicates that event.listen for pool is holding reference to engine even after session is garbage collected. *What is the right way/api to delete an engine ?* *UseCase* As there are lot of

Re: [sqlalchemy] SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
I tried session.bind.dispose() and NullPool. But engine *is still not cleared*. It still seems to have some reference from SessionEventsDispatch = sqlalchemy.event._DispatchDescriptor. On Friday, 11 January 2013 05:24:19 UTC+5:30, Michael Bayer wrote: On Jan 10, 2013, at 8:25 AM, Anoop K

Re: [sqlalchemy] SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
DefaultEngineStrategy = create I see event.listen(pool, 'first_connect', ...) event.listen(pool, 'connect', ...) But didn't find an equivalent event.remove ?? Anoop On Friday, 11 January 2013 11:03:57 UTC+5:30, Michael Bayer wrote: this is all about whatever you've done specifically. If you

[sqlalchemy] Re: SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
I tried the code in my setup.(SQLAlchemy-0.7.8-py2.6). Looks like engine did not got GCed. *[anoop@localhost tmp]$ p engtest.py * *about to delete sn...* *about to gc.collect()...* *Traceback (most recent call last):* * File engtest.py, line 31, in module* *assert engine_is_removed

Re: [sqlalchemy] Re: SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
*Great ...* Session(bind=engine, expire_on_commit=False) fixed the problem. Looks like 0.8.0b2 is BETA. Is it OK to use in production ? Thanks Anoop On Friday, 11 January 2013 11:48:29 UTC+5:30, Michael Bayer wrote: there's some side effect occurring as a result of how 0.7 creates a new

Re: [sqlalchemy] Re: SQLAlchemy Engine cleanup

2013-01-10 Thread Anoop K
, Anoop K wrote: I tried the code in my setup.(SQLAlchemy-0.7.8-py2.6). Looks like engine did not got GCed. *[anoop@localhost tmp]$ p engtest.py * *about to delete sn...* *about to gc.collect()...* *Traceback (most recent call last):* * File engtest.py, line 31, in module* *assert

[sqlalchemy] Re: when using sqlachemy autoload feature with oracle table column name coming in lower case even if in DB it is in upper case

2011-04-09 Thread Anoop
I run this script (myenv)anoop@AGLAP:~/Example/sqlalchemy$ python connect_sqlalchemy.py [u'id', u'first_name'] #Here I got column names in lower case Current normalize_method in (loc :/sqlalchemy/dialects/oracle/ base.py) def

[sqlalchemy] when using sqlachemy autoload feature with oracle table column name coming in lower case even if in DB it is in upper case

2011-04-06 Thread Anoop
') . . Now SQLServer +SqlAlchemy +autoload give upper case column names in upper case but when connecting with oracle upper case column names will be converted to lower case.Anybody have an idea why requires_quotes method is called like this? thanks: Anoop -- You received this message