session.query(User).
Is this possible? How would I do it?
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0x4543D577
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy
assigning new values to the columns
of the *same* object here. I think that may be what's causing your
problem. Try creating a new instance each time through the for newRec
in data: loop and see if the problem goes away.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0x4543D577
precisely
correspond to the real code (as with the creating a new mapper issue I
thought I'd spotted), that makes it even worse. I doubt anyone else
will be able to figure out your problem based on what you've given us
so far. (Although you never know, someone might surprise me).
--
Robin Munn
[EMAIL
/search?q=cache:HnC3ass1Y9YJ:en.wikipedia.org/wiki/Ilias_Lazaridis+ilias+lazaridishl=enct=clnkcd=1
I wasn't going to say anything unless someone responded to him, but in
the interests of pro-actively heading off a possible flamewar:
Please Don't Feed The Trolls. :-)
--
Robin Munn
[EMAIL PROTECTED]
GPG
-- that is, you
said something like Attivita.c.codice.in_('62601').
So change that in_() call to Attivita.c.codice.in_(*tuple(codice))
(or even just Attivita.c.codice.in_(*codice) for simplicity's sake)
and you should get the expected results.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0x4543D577
Date: Mon, 11 Dec 2006 13:28:25
From: Jose Soares [EMAIL PROTECTED]
To: sqlalchemy@googlegroups.com
Subject: [sqlalchemy] in_() function help
Date: Mon, 11 Dec 2006 13:27:58
From: Robin Munn [EMAIL PROTECTED]
To: sqlalchemy@googlegroups.com
Subject: Re: [sqlalchemy] in_() function help
Who
if there was a way to do that programmatically, it still
wouldn't look as good as the PDF output of a script specifically
designed to format Markdown (or HTML or whatever) into PDF.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0x4543D577
--~--~-~--~~~---~--~~
You
using the c = select(users)
method of constructing SQL queries, you'd have needed to run the
UPDATE statement by hand, by doing:
update(users.c.name=='Robin').execute(name='Robin Munn')
(Or by doing connection.execute('UPDATE users SET name ...') and so
on. As with the SELECT statements, SQLAlchemy
question.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0x4543D577
--~--~-~--~~~---~--~~
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
.
Maybe you can find a better chapter title here,
Constructing SQL *Commands* via Python Expressions, perhaps? But
that might make some people think not queries. Maybe statements
instead of commands...
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
/reload will provide performance gains in
both space and time.
And it would make my life quite a bit easier if I could use svnsync
instead of SVK. :-)
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
--~--~-~--~~~---~--~~
You received this message because you
!
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
--~--~-~--~~~---~--~~
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
will work.
It's still better to use False than 0, though, because that makes it
plain that it's a boolean value.
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
like that?
--
Robin Munn
[EMAIL PROTECTED]
GPG key 0xD6497014
--~--~-~--~~~---~--~~
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
14 matches
Mail list logo
