Re: [sqlalchemy] Generated update command is alway schosing alternative field names

2013-07-12 Thread Richard Gomes
I thought this could be of interest ot the mailing list: def select(self, table, index=None, *args, **kwargs): ''' Helper function which eases generation of SELECT statements using indexes. Arguments - table -- an instance of

[sqlalchemy] Generated update command is alway schosing alternative field names

2013-07-11 Thread Richard Gomes
hello, I've previously defined inserts and updates by hand in my application, which is working fine, not using SQLAlchemy at the moment. At this point, I'd like to employ SQLAlchemy to generate these inserts and updates for me. And that's all. I mean: just generate the queries for me. I'm *not*

Re: [sqlalchemy] Generated update command is alway schosing alternative field names

2013-07-11 Thread Simon King
On Thu, Jul 11, 2013 at 4:30 PM, Richard Gomes rgomes.i...@gmail.com wrote: hello, I've previously defined inserts and updates by hand in my application, which is working fine, not using SQLAlchemy at the moment. At this point, I'd like to employ SQLAlchemy to generate these inserts and

Re: [sqlalchemy] Generated update command is alway schosing alternative field names

2013-07-11 Thread Michael Bayer
On Jul 11, 2013, at 11:30 AM, Richard Gomes rgomes.i...@gmail.com wrote: hello, I've previously defined inserts and updates by hand in my application, which is working fine, not using SQLAlchemy at the moment. At this point, I'd like to employ SQLAlchemy to generate these inserts and

Re: [sqlalchemy] Generated update command is alway schosing alternative field names

2013-07-11 Thread Richard Gomes
Hello Michael, Thanks a lot for your help :) I've followed your directions. it works. Regarding the reserved column names (now I remember I saw this yesterday) ... it does not happen because I'm restricting the field names which appear in the SET clause, so that there's no collision between