On Wed, Sep 03, 2008 at 05:18:50PM +0200, Hermann Himmelbauer wrote:
Am Mittwoch 03 September 2008 16:02:17 schrieb Brian Sutherland:
On Wed, Sep 03, 2008 at 02:43:31PM +0200, Hermann Himmelbauer wrote:
Hi,
In my current SQLAlchemy / Zope-based design, I need the following:
-
Am Donnerstag 04 September 2008 09:10:22 schrieb Brian Sutherland:
On Wed, Sep 03, 2008 at 05:18:50PM +0200, Hermann Himmelbauer wrote:
Am Mittwoch 03 September 2008 16:02:17 schrieb Brian Sutherland:
On Wed, Sep 03, 2008 at 02:43:31PM +0200, Hermann Himmelbauer wrote:
Hi,
In my
Hermann Himmelbauer wrote:
[snip]
- The real reason I need the interfaces is that I have to include them in my
configure.zcml in order to make the underlying objects read/writeable. But
this is in my case only annoying, but not helpful at all.
Ah, interesting! This is a problem that doesn't
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,
Hey Hermann,
Hermann Himmelbauer wrote:
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
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
On Wed, Sep 03, 2008 at 02:43:31PM +0200, 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.
Am Mittwoch 03 September 2008 15:14:22 schrieb Martijn Faassen:
Hey Hermann,
Hermann Himmelbauer wrote:
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
Am Mittwoch 03 September 2008 16:02:17 schrieb Brian Sutherland:
On Wed, Sep 03, 2008 at 02:43:31PM +0200, Hermann Himmelbauer wrote:
Hi,
In my current SQLAlchemy / Zope-based design, I need the following:
- SQLAlchemy table definitions
- classes + mappers
- Zope interfaces
The
Hi there,
On Wed, Sep 3, 2008 at 4:34 PM, Hermann Himmelbauer [EMAIL PROTECTED] wrote:
[snip]
In megrok.rdb we've sketched out the reverse of your approach: derive
the Zope 3 schemas from the SQLAlchemy table definitions. This because
it's more easy to derive a basic schema from a table
Am Mittwoch 03 September 2008 17:30:23 schrieb Martijn Faassen:
Hi there,
On Wed, Sep 3, 2008 at 4:34 PM, Hermann Himmelbauer [EMAIL PROTECTED] wrote:
[snip]
In megrok.rdb we've sketched out the reverse of your approach: derive
the Zope 3 schemas from the SQLAlchemy table definitions.
11 matches
Mail list logo
