[sqlalchemy] Re: modifying a field

2010-06-22 Thread Aref
In this example I used: DB.password = 'hello' where passwod is the column name. Can I pass the column name in a variable? It does not seem that I could. I have tried different ways but none seems to work. Thanks. On Jun 20, 5:18 pm, Michael Bayer mike...@zzzcomputing.com wrote: On Jun 20, 2010,

[sqlalchemy] Referential integrity actions are not doing what I want

2010-06-22 Thread exhuma.twn
Hi, I have a table of items, where each item can be owned by one person, and held by someone else. I want the owner to be compulsory (not nullable), and the holder to be optional (nullable). To model this I have two tables, one for contacts and one for items. The item table has two fields

Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-22 Thread Michael Bayer
On Jun 21, 2010, at 7:52 PM, Jon Nelson wrote: On Mon, Jun 21, 2010 at 5:55 PM, Michael Bayer mike...@zzzcomputing.com wrote: not a bug, that's the correct behavior. Can you explain how it is correct? I asked for two things but I only got one. Why should it matter if they happen to be

RE: [sqlalchemy] Referential integrity actions are not doing what I want

2010-06-22 Thread King Simon-NFHD78
-Original Message- From: sqlalchemy@googlegroups.com [mailto:sqlalch...@googlegroups.com] On Behalf Of exhuma.twn Sent: 22 June 2010 14:27 To: sqlalchemy Subject: [sqlalchemy] Referential integrity actions are not doing what I want Hi, I have a table of items, where each

Re: [sqlalchemy] problem with select([table.c.column1, table.c.column1])

2010-06-22 Thread Jon Nelson
On Tue, Jun 22, 2010 at 8:55 AM, Michael Bayer mike...@zzzcomputing.com wrote: On Jun 21, 2010, at 7:52 PM, Jon Nelson wrote: On Mon, Jun 21, 2010 at 5:55 PM, Michael Bayer mike...@zzzcomputing.com wrote: not a bug, that's the correct behavior. Can you explain how it is correct? I asked

Re: [sqlalchemy] Referential integrity actions are not doing what I want

2010-06-22 Thread Michael Bayer
On Jun 22, 2010, at 9:27 AM, exhuma.twn wrote: Hi, I have a table of items, where each item can be owned by one person, and held by someone else. I want the owner to be compulsory (not nullable), and the holder to be optional (nullable). To model this I have two tables, one for contacts

[sqlalchemy] orm.joinedload() bug ?

2010-06-22 Thread Julien Cigar
Hello, I wondered why when using orm.joinedload() in an .options() on a Query it returns an AppenderQuery object, but when I user lazy='joined' it returns a mapped object (on 0.6.1) ? for example : ### with : http://pastebin.com/7NHeL8kd (lazy = dynamic) a = model.Content.query.options(

Re: [sqlalchemy] orm.joinedload() bug ?

2010-06-22 Thread Michael Bayer
On Jun 22, 2010, at 9:25 AM, Julien Cigar wrote: Hello, I wondered why when using orm.joinedload() in an .options() on a Query it returns an AppenderQuery object, but when I user lazy='joined' it returns a mapped object (on 0.6.1) ? for example : ### with :

Re: [sqlalchemy] orm.joinedload() bug ?

2010-06-22 Thread Julien Cigar
On 06/22/2010 18:13, Michael Bayer wrote: On Jun 22, 2010, at 9:25 AM, Julien Cigar wrote: Hello, I wondered why when using orm.joinedload() in an .options() on a Query it returns an AppenderQuery object, but when I user lazy='joined' it returns a mapped object (on 0.6.1) ? for example

[sqlalchemy] ALLCAPS datatypes

2010-06-22 Thread Ross Vandegrift
Hi everyone, I've been going through my app to prepare for an upgrade to SA 0.6 and was wondering what the deal is with the ALLCAPS vs. Capitalized data types. It looks like the ALLCAPS are designed to have the same name as the dialect specific types, while the Capitalized versions are designed

Re: [sqlalchemy] ALLCAPS datatypes

2010-06-22 Thread Michael Bayer
On Jun 22, 2010, at 5:56 PM, Ross Vandegrift wrote: Hi everyone, I've been going through my app to prepare for an upgrade to SA 0.6 and was wondering what the deal is with the ALLCAPS vs. Capitalized data types. It looks like the ALLCAPS are designed to have the same name as the