This issue seems to be causing me some trouble as well. Using
sqlalchemy-0.4.2dev_r3832, I'm getting the following error when
attempting to flush my session:
if not len(self._last_inserted_ids) or self._last_inserted_ids[0]
is None:
AttributeError: 'MSSQLExecutionContext_pyodbc' object has no attribute
'_last_inserted_ids'
I presume this is one of the unit tests that are currently failing,
but I wanted to mention that I'm experiencing trouble with this is in
practice as well. I get the same error in 0.4.0. I did not encounter
this problem in 0.3.x.
Let me know if a fix is not in the works for this issue and what I can
do to provide more helpful details.
Regards,
Jason
On Nov 25, 6:23 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Nov 25, 2007, at 5:46 PM, Paul Johnston wrote:
>
>
>
> > Hi,
>
> > I just realised, MSSQL is not returning last_inserted_ids correctly
> > when
> > an insert is done with multiple sets of params for a single
> > statement. I
> > don't think this is particularly a problem, just wanted to check what
> > the intention is.
>
> executemany() calls aren't supposed to return anything for
> last_inserted_ids. if you need last_inserted_ids you need to use
> individual insert executions.
--~--~---------~--~----~------------~-------~--~----~
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 to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
