Am Freitag, 13. April 2007 20:27 schrieb Kapil Thangavelu:
> i would suggest some alternatives approaches to consider first.
> potentially this would be easier going the other way around with zs2sa,
> and generating the mapper from there, you don't need to annotations as
> well since the zope schemas contain the relevant ui metadata, and the
> schema is the canonical definition of the rdb/sa schema. bonus is you get
> multidb support for the schema, as an example of doing things this way,
> the transmute funcction has the options of specifying base interfaes, so
> you also have the option at the risk of ordering dependencies of replacing
> the iface class thats a base arg to the transmute function with the result
> of the transmute function, presumably though if this being done in the
> same module (interfaces.py) then its not an issue though.
Interesting approach, however, I doubt this is going to work when one has to
access an existing relational database - like in my case. After all one has
once again redundant definitions.
Therefore in cases where the database is designed together with the Zope3
application, the transmute function could be an interesting approach, but in
cases where the DDL-statements already exist, the generation of schemas out
of the table definitions seem to be the better way.
Moreover I'm also curious if advanced table definitions such as constraints,
checks and the like can be generated from Zope schemas.
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7
Zope3-users mailing list