On Thu, Oct 09, 2003 at 08:46:24PM -0700, Jason Corbett wrote:
Thanks for your reply. I've actually been thinking in
an object oriented form for a while. I've looked at
implimenting this project in Java using either
prevailance or a object persistence model that mapped
to a RDBMS. I like
On Fri, 2003-10-10 at 05:51, Bjorn Stabell wrote:
From: Paul Winkler [mailto:[EMAIL PROTECTED]
On Thu, Oct 09, 2003 at 08:46:24PM -0700, Jason Corbett wrote:
How does an object in zope know where it sits in the hirearchy,
The only unique identifier that zope provides is
the
Hi Jason,
if you want to deal with references and unique ids and that stuff, feel
free to take a look at http://plone.org/development/current/projects/Ticle
and perhaps to contribute your ideas or even sourcecode.
-sp
___
Zope-Dev maillist -
Jason Corbett wrote at 2003-10-9 20:46 -0700:
...
How does an object in zope know where it sits in the
hirearchy, and how does it reach other objects.
In fact, the object does not know it.
In Zope, you usually do not deal with the object itself
but with an acquisition wrapper. This
On Thu, Oct 09, 2003 at 05:07:28PM -0700, Jason Corbett wrote:
to reference in some intelligent way between objects
in zope, and I need a way to query for a list of them.
google for mxmRelations. It does many-to-many
relationships so yuo might have to modify it a bit
if you really need to
Hi Jason,
I am not a zope developer, I am a semi-new user who started with zope
coming from the same mindset as yourself. One of the biggest challanges(at
least for me) is to wrap your mind around object oriented programming. The
zope database is an object oriented database. This means that you
Thanks for your reply. I've actually been thinking in
an object oriented form for a while. I've looked at
implimenting this project in Java using either
prevailance or a object persistence model that mapped
to a RDBMS. I like the idea of zope, so maybe I
should clarify my question:
How does an
On Fri, 2003-10-10 at 00:46, Jason Corbett wrote:
Thanks for your reply. I've actually been thinking in
an object oriented form for a while. I've looked at
implimenting this project in Java using either
prevailance or a object persistence model that mapped
to a RDBMS. I like the idea of
I'm sorry for my ignorant use of the terms relation
and relationship. I'll try to use the terms more
appropriately in the future.
I think I understand where I've become confused. In
many of the persistance mechanisms I've looked at
references to other objects were handled specially,
and had
