Hi.
I want to disable aliasization in eager loading query generation.
Is this possible?
Thanks Manlio Perillo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email
Hi.
I have noted that subqueries in sess.query does not get correlated.
Is this a feature or a bug?
Thanks Manlio Perillo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this
Hi,
I'm using straight kinterbasdb connections to firebird in a
multithreaded SocketServer, and actually I open a new connection at
every request. Searching for a connection pooling solution I found that
pool.py sqlalchemy can be great for my needs.
I whish modify my application so it can
need an example.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
in theory the connections to the original database should become
invalidated when the cursor() function on the connection throws an
error. an invalidated connection will then try to connect again on the
next reuse which will call your function.
however in practice ive noticed thats cursor() is
Hi all,
while trying the ORM side of sqlalchemy, I noticed a remarkable speed
difference
between using the ORM machinery and the plain db access.
The attached test consists of 1000 inserts and 1000 selects; its
purpose is
just to test the overhead of the data mapping system.
The ORM version
the ORM is going to be slower in all cases since there is the overhead
of creating new object instances and populating them, as well as
initializing their attribute instrumentation and also a copy of their
attributes for the purposes of tracking changes when you issue a
flush() statement. this
Here are the usual suspects and versions
1. Ubuntu Edgy 6.10 (Linux Distribution)
2. Python 2.5 Final
3. PostgreSQL 8.1.4
4. SQLAlchemy 0.2.8-1 or 3.3
5. python-psycopg2 version 2.0.5.1-1.
I am having a serious lockup problem. The summary is I am following the
tutorial to the letter. When it
Here are the usual suspects and versions
1. Ubuntu Edgy 6.10 (Linux Distribution)
2. Python 2.5 Final
3. PostgreSQL 8.1.4
4. SQLAlchemy 0.2.8-1 or 3.3
5. python-psycopg2 version 2.0.5.1-1.
I am having a serious lockup problem. The summary is I am following the
tutorial to the letter. When it
Hi All,
Happy X'max :)
I'm implementing a tag schema using sqlalchemy, I follow the official
document's way:
articles_table = Table('articles', metadata,
Column('article_id', Integer, primary_key = True),
Column('headline', String(150), key='headline'),
Column('body', TEXT,
as mentioned on IRC, you have to lose your reference to the ResultProxy
first (or close() it) so that the underlying connection is returned to
the connection pool, where it has a ROLLBACK issued on it. this will
release the locks so that other connections can drop the table. in the
case of
the tables have all foreign key relationships, but the buggy software I
use (db designer) forgot to print it out
I will set up a complete testcase now that tries to do what I want to
do. but do you see any problems in general to relate from one
association object to another?
Dennis
Michael Bayer wrote:
the ORM is going to be slower in all cases since there is the overhead
of creating new object instances and populating them, as well as
initializing their attribute instrumentation and also a copy of their
attributes for the purposes of tracking changes when you issue a
Michael Bayer ha scritto:
need an example.
from sqlalchemy import *
db = create_engine('postgres://manlio:[EMAIL PROTECTED]/test')
metadata = BoundMetaData(db)
programmers = Table(
'programmers', metadata,
Column('name', String, primary_key=True)
)
languages = Table(
the eager load queries are not meant to be modified by the query that
you send to query.select()youre not really supposed to have any
awareness of the eager loads at all. eager loading and lazy loading
both load the full list of child items in all cases. heres a relevant
FAQ entry:
its a bug. its fixed in revision 2173.
--~--~-~--~~~---~--~~
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
you can close on the result returned by the execute() call. however,
if you just lose the reference to the result, that is as good a close
since python's garbage collection can clean it up. also, you arent
usually going to have code as in your example that locks that harshly
(i.e. youll find
you should write this code against the 0.3 series since the
organization of MapperProperty objects is a little better. but also,
im not sure if traversing mapper.props() is the best way to go here
(also what is mapped_class.c.self ? easier to say
class_mapper(someclass)...) ...why not just
without the foreignkeys i cant tell much. i dont see anything
obviously wrong with it. would also need to see how you are creating
the objects/assigning/etc. thats why the simple one-file testcase
says it all...your tables, your mappers, what youre doing exactly to
create the issue, heres
ive committed in r2174 some speed enhancements, not including the
abovementioned change to deferring the on-load copy operation (which
is a more involved change), that affords a 20% speed improvement in
straight instance loads and a 25% speed improvement in instances loaded
via eager
Michael Bayer wrote:
the startswith/endswith functions are just sticking a % on either
side of a string argument and using LIKE. im not exactly sure how they
could accept a bindparam argument since there is a string concatenation
that must take place within the python space.
Since the
21 matches
Mail list logo
