Thanks a lot! The solution is so simple that I feel a little
embarassed...
On 16 Okt., 18:15, Michael Bayer [EMAIL PROTECTED] wrote:
On Oct 16, 2007, at 10:45 AM, klaus wrote:
The only thing that I could find out about the reason is that in
engine/base.py (1290)
I've been struggling with this problem for a long time now and will
appreciate any help.
I'm using Oracle and pass users/passwords to access the database.
uri = 'oracle://' + config.get('sqlalchemy_conf.webuser', '') + ':' +
config.get('sqlalchemy_conf.webpassword', '') + '@' + bd_location
On Oct 16, 11:13 pm, Eddie [EMAIL PROTECTED] wrote:
Having problems all day connecting and tried various apps just in
case... is there anyway I could get someone to zip and host this
really quick?
Error * PROPFIND request failed on '/sqlalchemy/trunk' PROPFIND of '/
sqlalchemy/trunk':
On Oct 16, 7:42 pm, Michael Bayer [EMAIL PROTECTED] wrote:
On Oct 16, 2007, at 1:30 PM, [EMAIL PROTECTED] wrote:
Am I really supposed to save/flush/clear/query my objects to get the
correct mappings?
Or is this a bug?
the advised pattern here is the
association object pattern
On Oct 17, 12:21 pm, Thomas Wittek [EMAIL PROTECTED] wrote:
mapper(Participation, participation_table,
properties=dict(
user=relation(User, backref='participations')
)
)
Should be:
mapper(Participation, participation_table)
Hi,
Here's how it should work: every time the user logs in, SA creates a
new engine with his log/pass or uses the one that was already opened
and then uses it.
Unless something has changed recently, this pattern is not particularly
supported.
Still, you could probably get it working with
Thanks a lot, Paul. Great point, works just great.
That pretty much solved the issue.
log_dic
log_typle = (session['login'], session['password'])
if not log_dic.has_key((log_typle)):
engine = create_engine(uri)
log_dic[log_typle] = engine
On Oct 17, 2007, at 4:07 AM, klaus wrote:
Thanks a lot! The solution is so simple that I feel a little
embarassed...
im embarrased that bug's been present for so long !
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
How I can chek if a orm class is in a session ?
--~--~-~--~~~---~--~~
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,
On Oct 17, 2007, at 11:31 AM, Expo wrote:
How I can chek if a orm class is in a session ?
the session supports __contains__() . Details on session attributes
are at http://www.sqlalchemy.org/docs/04/
session.html#unitofwork_using_attributes .
Hey list -
I'm very happy to announce that we've put out 0.4.0 final. Thanks
to all the contributors as well as all the beta testers who have
helped us move through six beta releases, just to make sure we've got
everything right (or as much right as we can). For those still
working
..coincidentally released on the self-same day when I am finally taking the
wraps off 0.4.0 for a spin on a new project.
Congrats on this huge release, everybody!
On 10/17/07, Michael Bayer [EMAIL PROTECTED] wrote:
Hey list -
I'm very happy to announce that we've put out 0.4.0 final.
Am Mittwoch, 17. Oktober 2007 21:40 schrieb Michael Bayer:
Hey list -
I'm very happy to announce that we've put out 0.4.0 final. Thanks
to all the contributors as well as all the beta testers who have
helped us move through six beta releases, just to make sure we've got
everything right
I have a question about inconsistency in unicode handling when using a
bindparam explicitly and when using a literal when constructing my
query. It appears that if I use a unicode object in the actual query
whereclause, the convert_bind_param function of the base String will
get called(query1).
On Oct 17, 2007, at 7:41 PM, dykang wrote:
query2 = sqlalchemy.select([test],
sqlalchemy.and_ (
test.c.id == sqlalchemy.bindparam ('id'),
test.c.name == sqlalchemy.bindparam('name'),
)
)
currently you'd have to say test.c.name == bindparam('name',
Btw this is fixed in SQLAlchemy 0.3.11.
--~--~-~--~~~---~--~~
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
On Oct 17, 2007, at 8:49 PM, dihde14 wrote:
Btw this is fixed in SQLAlchemy 0.3.11.
oh, sorry ! missed your original email in the crowd. yes this was
ticket #768.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
17 matches
Mail list logo
