[Zope3-dev] Re: Zope 3 web root

Shaun Cutts shaun at cuttshome.net
Tue Feb 14 01:37:59 EST 2006


Here here! I'm just learning to cross the gap starting from the RDBMS
side. Just our initial deployment will have a DB growing by about 30K
numbers per day, day in and day out. There are various workflows that
are driven by this data. The parts of these that need people are now
supposed to be available via Zope3.

In my case, the business logic is in python, so I don't need (or want)
to access the db directly, but I do need "hollow", paged containers that
live in the ZODB themselves but display data that lives elsewhere. I've
started implementation, (... stumbling along so far... any comments on:

 Re: [Zope3-Users] newbie design questions for UI to external data

would be welcome!)

- Shaun

-----Original Message-----
From: zope3-dev-bounces+shaun=cuttshome.net at zope.org
[mailto:zope3-dev-bounces+shaun=cuttshome.net at zope.org] On Behalf Of
Martin Aspeli
Sent: Monday, February 13, 2006 5:37 PM
To: zope3-dev at zope.org
Subject: [Zope3-dev] Re: Zope 3 web root

On Mon, 13 Feb 2006 07:51:34 -0000, Chris Withers
<chris at simplistix.co.uk>  

> Scripts and RBDMS are the fast food of the web development world, not

> the salad. Looks nice, tastes great, eventually leaves you fat and  
> unhealthy. ZODB and maybe an ORM is the greens for me, it might not be

> to everyone's taste at first, but it's the best option in the long

I think that's certainly true for content-centric applications, which is

what people seem to build the most of in Zope. But if you were storing
million records of numbers and short strings that you needed to query  
across multiple dimensions, you'd probably put them in postgresql.

Zope 3 should really have a better story on SQL. Not replace the ZODB,
show how in your code you best deal with an RDBMS. I think that should  
leverage existing python APIs and ORM tools (I think there's a place for

both SQL-style queries and ORM, depending on how much you need "ad-hoc"

queries or at least complex, one-off representations of data, and how
you need one logical view of your data), but there should be patterns
integration layers (if needed) to show how to get data from an RDBMS
a view, how to make an edit form for that data, and how to integrate
with the rest of your probably content-centric application.



Zope3-dev mailing list
Zope3-dev at zope.org

More information about the Zope3-dev mailing list