Hi,
I've implemented a site that uses both Principal (for external users)and
PAU (for intranet users).
It use a customized skin and in the template.pt file I want to print out
the username.
The following line works if I'm connected as an external user (defined
in principals.zcml)
Hi all,
I am really need some help getting my first pluggable authenticator to be
consulted by zope.
I have followed the examples in the app/authentication README to create a
credentials plugin, authenticator plugin etc., what I want to do now is
register the plugins using zcml. I have tried us
Hi all,
I'm a newbie to zope3, but I've been looking through google, the zope3
apidoc, the books by weithershausen and richter and can't find the
solution to my problem.
I've added two items to the zmi_views menu. One is an browser:editform
(named AddProject.html), and the other is a browser
On Tue, Jul 11, 2006 at 06:43:12PM +, eleanor weavers wrote:
> I have followed the examples in the app/authentication README to create a
> credentials plugin, authenticator plugin etc., what I want to do now is
> register the plugins using zcml. I have tried using the the "utility" tag in
> th
Hi,
there was a discussion about the bad idea to simulate a relational
database in ZODB using indexes and unique ids. So I wonder what's the
"correct" way to express a n:m realtionship between objects.
For example: I have projects and articles. An article might be relevant
for multiple proje
Am 11.07.2006 um 23:17 schrieb Achim Domma:
Hi,
there was a discussion about the bad idea to simulate a relational
database in ZODB using indexes and unique ids. So I wonder what's
the "correct" way to express a n:m realtionship between objects.
For example: I have projects and articles.
Em Ter, 2006-07-11 às 23:17 +0200, Achim Domma escreveu:
> Hi,
>
> there was a discussion about the bad idea to simulate a relational
> database in ZODB using indexes and unique ids. So I wonder what's the
> "correct" way to express a n:m realtionship between objects.
In usual Object Oriented m
Leonardo Rochael Almeida wrote:
In usual Object Oriented modeling, an n:m relationship is usually
modeled as a collection of relationship objects each one keeping one
direct reference to each side of the relationship. Of course, using
these systems that already try to model relationships helps y
What you describe sounds perfectly fine.
You might want to consider exposing the actual IArticleProjectRelation
object eventually if you decide to hang other attributes to it, say a
'start date'.
Cheers, Leo
Em Qua, 2006-07-12 às 00:40 +0200, Achim Domma escreveu:
> Leonardo Rochael Almeida wrot
