Hi Hermann, I'm currently using ore.alchemist to map sqlalchemy tables to zope3 schemas. Ok, so I had to tweak a couple of stuff but the end result is that I have objects which are mapped to rdbms tables via sqlalchemy and I can use generic formlib forms which decreases my development time for new features. So my advice is checkout alchemist and ore.alchemist, it worked for me. Regards Francois Lubbe PS: the reason I had to tweak stuff is because I'm migrating from ZPatterns on Zope 2.7.8 to ore.alchemy/sqlalchemy on Zope 2.10.4 and I needed to have both Zpatterns and ore.alchemy running on the same instance as migrating everything at once was not a viable option. David Pratt wrote:
You may wish to look at z3c.dobbin, though the issue I have found in my own experimentation, is with association tables for many to many relationships which throws in a wrench into this otherwise elegant solution. There may be something to around this in future.
Hermann Himmelbauer wrote:
Hi, In my current SQLAlchemy / Zope-based design, I need the following:
- SQLAlchemy table definitions - classes + mappers - Zope interfaces
The problem with this design is that much data has to be defined twice, e.g. the datatype "varchar(50)" should be represented by an interface with TextLine(max_length="50"). Moreover, any changes such as adding columns etc. also have to be done in the interface and the table definition.
To overcome this, I just had the idea to use the interface/schema definitions for the table definition itself. Probably I'm not the first who had this idea, but I'm not aware of such an extension to interfaces.
Any thoughts on this?
Best Regards, Hermann
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )