[sqlalchemy] Re: Insert.params() broken?

2008-11-21 Thread bukzor
On Nov 20, 7:39 pm, Michael Bayer [EMAIL PROTECTED] wrote: On Nov 20, 2008, at 9:05 PM, bukzor wrote: Would it make sense to rename Insert.values to Insert.params? Or make Insert.params call Insert.values. It seems quite strange for an object to have functions that aren't usable...

[sqlalchemy] Re: Insert.params() broken?

2008-11-21 Thread bukzor
On Nov 20, 6:20 pm, Empty [EMAIL PROTECTED] wrote: Different, but related question: How do I print out the statement in copy-paste-able format? More specifically, how do i get an ordered list of bound values out of the statement? This code does what I want, but it's really clunky and

[sqlalchemy] Re: Insert.params() broken?

2008-11-20 Thread Michael Bayer
On Nov 20, 2008, at 6:16 PM, bukzor wrote: The second crashes with: File /tools/aticad/1.0/external/python-2.4.1/lib/python2.4/site- packages/SQLAlchemy-0.5.0rc4-py2.4.egg/sqlalchemy/sql/expression.py, line 3515, in _copy_internals self.parameters = self.parameters.copy()

[sqlalchemy] Re: Insert.params() broken?

2008-11-20 Thread bukzor
When you say generative, do you mean it returns a new object, as opposed to in-place changes? Would it make sense to rename Insert.values to Insert.params? Or make Insert.params call Insert.values. It seems quite strange for an object to have functions that aren't usable... Different, but

[sqlalchemy] Re: Insert.params() broken?

2008-11-20 Thread Michael Bayer
On Nov 20, 2008, at 9:05 PM, bukzor wrote: When you say generative, do you mean it returns a new object, as opposed to in-place changes? Would it make sense to rename Insert.values to Insert.params? Or make Insert.params call Insert.values. It seems quite strange for an object to have