"R. David Murray" wrote:
This means you can do things like
have (my example) a Paradox database of books, authors, and a
books-to-authors map, and have Author and Book objects in the system
such that a Book has a list of its Author objects and the Author
has a list of its Book objects, all
Joachim Werner wrote:
And, instead of switching back-ends in ZPatterns, I could as well
just rewrite my non-ZPattern objects to work with the new back-end,
which doesn't seem to be more work.
Well, do your first project both ways. It would make an interesting
comparative study.
I
"R. David Murray" wrote:
Let me be a bit less cryptic. Design your system, and use ZPatterns, and you
can defer questions about which storage suits the parts of the app until
later, and can change your mind at need. For the kind of project you
are embarking upon, the time needed to learn
On Sat, 17 Feb 2001, Doug Hellmann wrote:
I've yet to see any documentation which sufficiently explains what
ZPatterns is and how to use it for me to consider it in any of my
projects. I've read the wiki pages and I just don't get it.
Where should I be starting for enlightenment?
Well, if
Hi!
We are currently developing a groupware system with Zope. As usual, the options
for the storage back-end are using a SQL DB (postgres, ...) or ZODB.
I know that this question has been asked a thousand times. But I'll repeat it
for our specific situation:
SQL or ZODB+ZCatalog, which one
On Sat, 17 Feb 2001, Joachim Werner wrote:
SQL or ZODB+ZCatalog, which one is better?
Any comments?
Just the obvious one: ZPatterns. grin.
--RDM
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No
Let me be a bit less cryptic. Design your system, and use ZPatterns, and you
can defer questions about which storage suits the parts of the app until
later, and can change your mind at need. For the kind of project you
are embarking upon, the time needed to learn ZPatterns is well worth it.
"R. David Murray" wrote:
Let me be a bit less cryptic. Design your system, and use ZPatterns, and you
can defer questions about which storage suits the parts of the app until
later, and can change your mind at need. For the kind of project you
are embarking upon, the time needed to learn
