[Zope-DB] Re: Example for RDB persistency in zope products?

Nick Bower nicholas.bower at jrc.it
Sat Jun 26 06:21:38 EDT 2004


Thanks.  I've been using TTW ZSQLs for 6 months now, but they (and 
anything else TTW apart from ZPT etc) produce an application that is not 
scalable imho.  Great for prototyping however and that's exactly what I 
used them for.

Maybe what Dieter is suggesting is a good compromise.

Igor Elbert wrote:

> Method 2 has some advantages:
>  - You can use DTML in your ZSQLs, edit and test ZSQLs TTW
>  - The details of the database connection are handled by Zope DA object so
> in your product you don't have dependency on psycopg, DCOracle2, etc
> 
> Igor
> 
> ----------------------------------------------------------------------------
> -------------------------------
> Does anyone have any examples of how I code relational database
> persistency into an object (at a Zope product level)?
> 
> I've an application written to view and manage complex organisational
> data in Python scripts, ZPTs and ZSQL methods, and would like to move it
> to the product level and into persistent object land.  However, the RDB
> persistency aspect is what I'm most confused about.
> 
> I've seen people talk about doing the following:
> 
> 1. Inherit from ZSQL methods for their business objects
> 2. Call ZSQL methods from their business object logic
> 3. Using an existing DA, such as psycopg, directly, bypassing ZSQL
> methods, and calling the DA connection methods from business logic
> 4. Writing their own DA for integration with business logic
> 
> 3. would have seemed to me like the practical way to go, but I'm just
> not sure where to start for lack of documentation promoting any way
> other than using ZSQL.
> 
> Nick
> 
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.



More information about the Zope-DB mailing list