[Zope3-Users] zalchemy integration
ccardelli at iv-srl.it
Thu Aug 10 03:46:28 EDT 2006
David Pratt wrote:
> Hi Carlo.
> As a workaround to get objects into the db you can comment out the
> following lines in checkName like this:
> def checkName(self, name, container):
> if isinstance(name, str):
> name = unicode(name)
> elif not isinstance(name, unicode):
> raise TypeError("Invalid name type", type(name))
> #unproxied = removeSecurityProxy(container)
> #if not name.startswith(unproxied._class.__name__+'.'):
> # raise UserError("Invalid name for SQLAlchemy object")
> return True
I actually worked around it as following:
unproxied = removeSecurityProxy(container)
-> if not ISQLAlchemyContainer.providedBy(unproxied):
-> return NameChooser.checkName(self, name, container)
if not name.startswith(unproxied._class.__name__ + '.'):
raise UserError("Invalid name for SQLAlchemy object")
even if the 'else' case seems unused: i.e., this method is not called
while adding a SQLAlchemyContainer.
Once skipped this, the process halted while adding the 'blank' object to
the db: in zope.app.container.browser.adding, in the method add(), the
following lines failed:
container[name] = content
... one ininfluent-for-this-problem line ...
Here, the last line failed because the SQLAlchemyContainer completely
disregards the "name" attribute (as specified in container.txt), so
retrieving data using the same name is not possible.
Maybe I could spend some time in it, but this "basic" problem leads me
to some doubt about the state of the zalchemy package and its
integration with Zope3.
In the mailing list archives I found some discussion about ORM problems
(2-phase commit, thread support and so on) but nothing specific about
zalchemy, and (as far as I can see) no "definite" solution on the
Could someone tell the current state-of-the-art about this, or his/her
experience about integrating sqlalchemy in other ways?
Thank you in advance.
More information about the Zope3-users