Using SQLAlchemy with Plone/Zope

[Mike]

Hi,

We are using SQLAlchemy 4.X in Zope using SQLAlchemyDA, found here:

http://opensource.zopyx.com/projects/SQLAlchemyDA

This uses SA 0.4.0. We are connecting to MS SQL 2000. While this works
in Zope for normal SQL commands, if we try to execute a stored
procedure, we get the following traceback:


[Traceback (most recent call last):
File "sqltest.py", line 14, in ?
print cur.fetchall()
File "/opt/Plone-2.5/Python-2.4.3/lib/python2.4/site-packages/
SQLAlchemy-0.4.0-py2.4.egg/sqlalchemy/engine/base.py", line 1231, in
__repr__
return repr(tuple(self))
File "/opt/Plone-2.5/Python-2.4.3/lib/python2.4/site-packages/
SQLAlchemy-0.4.0-py2.4.egg/sqlalchemy/engine/base.py", line 1223, in
__iter__
yield self.__parent._get_col(self.__row, i)
File "/opt/Plone-2.5/Python-2.4.3/lib/python2.4/site-packages/
SQLAlchemy-0.4.0-py2.4.egg/sqlalchemy/engine/base.py", line 1468, in
_get_col
rec = self._key_cache[key]
AttributeError: 'ResultProxy' object has no attribute '_key_cache'


I'm not sure how to go about troubleshooting this. Would upgrading it
to SQLAlchemy 0.4.5 fix it? Any hints would be appreciated.

Thanks a lot!

Mike

[Andreas Jung]

You're basically on the wrong list. This issue belong on the SQLAlchemy
mailing list. There is no indication for a anything related to Zope.

> Would upgrading it
> to SQLAlchemy 0.4.5 fix it?

Try it out yourself and see what's happening. Nobody know about your
particular setup, code etc. - but you do.

Andreas

[Mike]

On May 16, 11:06 am, Andreas Jung <li...@zopyx.com> wrote:

I'm confused. This IS the SqlAlchemy list...

> > Would upgrading it
> > to SQLAlchemy 0.4.5 fix it?
>
> Try it out yourself and see what's happening. Nobody know about your
> particular setup, code etc. - but you do.
>
> Andreas
>

We did end up trying it soon after posting and it works now. Sorry to
bother you.

Mike

[Andreas Jung]

Sorry, you're on the right list. Somehow I saw this mail in the context
of the Zope lists.

Andreas

[Michael Bayer]

On May 16, 2008, at 11:58 AM, Mike wrote:

>
>
> I'm not sure how to go about troubleshooting this. Would upgrading it
> to SQLAlchemy 0.4.5 fix it? Any hints would be appreciated.
>

Hi Mike -

yeah, i see your stacktrace is from 0.4.0 and i have a vague
recollection of some ResultProxy bug of that nature back then, so an
upgrade should fix it (current version is 0.4.6).

- mike