Hi there,
A few contributions to this interesting discussion...
[snip the Zope 3 catalog is not a hack, and clean and simple]
The catalog and index code is not a hack, and is in fact simple,
effective and flexible. Python is the query language, and the lack of
an optimizer is not a reason
I'm not convinced that Florent blog entry says what Gary thinks it
does, but I agree with Gary on the other stuff: It should be possible
by configuration, to switch out at least some parts to a relational
database.
The catalog indexes and metadata is a prime example of this. No, there
is nothing w
I'm having problems with using .
I have an interface:
class ISzerep(Interface):
name = TextLine(
title=u"Szerep nev",
description=u"Szerep nev",
required=True
)
szemelyek = List(
title=u"Hozzarendelt szemelyek",
description=u"Hozzarendelt sze
On Aug 23, 2005, at 3:44 PM, Janko Hauser wrote:
Am 23.08.2005 um 20:36 schrieb Shane Hathaway:
Gary Poster wrote:
On Aug 23, 2005, at 1:11 PM, Gary Poster wrote:
Argh, communication. That still could be too-easily
misinterpreted, and I didn't stare at it long enough before I
sent
Martijn Faassen wrote:
> Missing powerful query concepts
> ---
>
> Certain powerful query concepts like joins, available in a relational
> setting, are missing. I've already run into a scenario where I wanted to
> someting like this: given a bunch of version objects wit
Adam Groszer wrote:
I'm having problems with using .
I have an interface:
class ISzerep(Interface):
name = TextLine(
title=u"Szerep nev",
description=u"Szerep nev",
required=True
)
szemelyek = List(
title=u"Hozzarendelt szemelyek",
description=u"H
On 8/24/05, Adam Groszer <[EMAIL PROTECTED]> wrote:
> If I modify the addform configuration by adding the :
> schema="szscreen.interfaces.ISzemely"
> content_factory="szscreen.app.Szemely"
> label="Uj Szemely"
> name="AddSzemely.html"
> permission="zope.ManageConten
Yesterday I made a change to the Zope 3 trunk that changes how the
ZCML slugs from the package-includes/ directory are handled.
If you're not accustomed to using "make" to build the software (at
least on non-Windows platforms), you might want to run "make" at least
once.
Here's what changed: The
On Aug 24, 2005, at 6:27 AM, Martijn Faassen wrote:
Hi there,
A few contributions to this interesting discussion...
[snip the Zope 3 catalog is not a hack, and clean and simple]
The catalog and index code is not a hack, and is in fact simple,
effective and flexible. Python is the query
On Aug 24, 2005, at 8:08 AM, Lennart Regebro wrote:
I'm not convinced that Florent blog entry says what Gary thinks it
does,
Hopefully you can see where I would get my interpretation, though.
I'm happy to have Florent clarify on his return. This is a good
discussion in any case.
but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
Thanks for both posts. I followed up with some additional notes in my blog:
http://palladion.com/home/tseaver/obzervationz/ecms_rdbms_vs_zodb_20050823
Tres.
- --
On 8/24/05, Gary Poster <[EMAIL PROTECTED]> wrote:
> Hopefully you can see where I would get my interpretation, though.
Yup.
> ZODB catalog story has compelling advantages over an RDBMS catalog,
> in addition to disadvantages.
I'm sure they do, although I'm not immediately aware of them (I would
Paul Winkler wrote:
Martijn Faassen wrote:
Missing powerful query concepts
---
Certain powerful query concepts like joins, available in a relational
setting, are missing. I've already run into a scenario where I wanted to
someting like this: given a bunch of version
En/na [EMAIL PROTECTED] ha escrit:
Martijn Faassen wrote:
Missing powerful query concepts
---
Certain powerful query concepts like joins, available in a relational
setting, are missing. I've already run into a scenario where I wanted to
someting like this: given
Gary Poster wrote:
On Aug 24, 2005, at 6:27 AM, Martijn Faassen wrote:
[snip]
Now as to where I see areas where features are lacking in the Zope 3
catalog:
Underfeatured query API
---
[snip query API discussion]
Another way of looking at this--or simply an additional f
Am 24.08.2005 um 18:02 schrieb Martijn Faassen:
Yes, this is bringing the transparency a step further. Basically
what you'd be doing is building an object relational abstraction
based on the Zope catalog. :)
Interestingly the discussion has gone from a general concern of the
usage of RDB
On Aug 23, 2005, at 8:07 PM, Michel Pelletier wrote:
On Tue, 2005-08-23 at 18:04 -0400, Gary Poster wrote:
The relationship between ZODB content objects, their int id as
provided by the pertinent intid utility, and a (theoretical)
corresponding RDF URI is what I'm having a hard time not maki
Hi!
Somehow related to the discussion on optimizing catalog queries, I have
been thinking about how to best implement local portlets in cpsskins in
terms of scalability, performance and functionality. The implementation
is heavily dependent on being able to performance effective catalog
queries (
Martijn Faassen wrote at 2005-8-24 17:28 +0200:
> ...
>In your example you haven't done a join as I describe above, unless I
>miss something. The essential part is that I want an object with state
>'PUBLISHED' unless there is another object where field 'ID' is the same
>as this object that is wi
Martijn Faassen wrote at 2005-8-24 12:27 +0200:
> ...
>Underfeatured query API
>---
>
>I do think that currently the API to query it is woefully underfeatured.
>
>I've tried to work on this problem and am sitting on some code that just
>needs a bit of time to polish and release
On Aug 24, 2005, at 2:24 PM, Jean-Marc Orliaguet wrote:
Hi!
Somehow related to the discussion on optimizing catalog queries, I
have
been thinking about how to best implement local portlets in
cpsskins in
terms of scalability, performance and functionality. The
implementation
is heavily
This is a general reply, Martijn just summed up many of the points so
nicely (as usual) that I'm using his email as a starting point...
> From: Martijn Faassen <[EMAIL PROTECTED]>
> Subject: Re: [Zope3-dev] Florent's O-R blog entry
> I have had some opportunity to work with the Zope 3 catalog re
On Wed, 2005-08-24 at 12:39 -0400, Gary Poster wrote:
> The Zope 3 back end for RDFLib allows you to use any intid-registered
> object as a resource, as long as they are adaptable to
> rdflib.interfaces.IURIRef. The Zope 3 back end package provides a
> simple adapter for all Zope content ob
On Wed, 2005-08-24 at 15:28 -0400, [EMAIL PROTECTED] wrote:
> Message: 5
> Date: Wed, 24 Aug 2005 20:24:30 +0200
> From: Jean-Marc Orliaguet <[EMAIL PROTECTED]>
> Subject: [Zope3-dev] [DRAFT] local portlets and perspectives
> It is built on the notion of "Perspective" (see the link) and on the
>
Gary Poster wrote:
>
> On Aug 24, 2005, at 2:24 PM, Jean-Marc Orliaguet wrote:
>
>>
>> Hi!
>>
>> Somehow related to the discussion on optimizing catalog queries, I have
>> been thinking about how to best implement local portlets in cpsskins in
>> terms of scalability, performance and functionali
Michel Pelletier wrote:
>On Wed, 2005-08-24 at 15:28 -0400, [EMAIL PROTECTED] wrote:
>
>
>
>>Message: 5
>>Date: Wed, 24 Aug 2005 20:24:30 +0200
>>From: Jean-Marc Orliaguet <[EMAIL PROTECTED]>
>>Subject: [Zope3-dev] [DRAFT] local portlets and perspectives
>>
>>
>
>
>
>
>>It is built on the
On Thu, 2005-08-25 at 04:10 +0200, Jean-Marc Orliaguet wrote:
> You would need a quadruple store in that case (see the previous mail) -
rdflib.Graph is actually a quadruple store. Many users still say
TripleStore because that was the old class name, but most RDF systems,
rdflib included, have gr
On Wed, 2005-08-24 at 22:25 -0400, [EMAIL PROTECTED] wrote:
> Subject: Re: [Zope3-dev] [DRAFT] local portlets and perspectives
> > It is built on the notion of "Perspective" (see the link) and on the
> > idea of querying the catalog using triadic relations instead of joining
> > sets of query re
28 matches
Mail list logo
