Hello:
Potentially stupid question: is a query that spans multiple catalogs
analogous to a relational query that spans multiple tables?
A relational query that spans multiple tables is analyzed by the query
optimizer to make maximal use of indices.
One can also optionally pass in "hints" to
On Aug 31, 2005, at 5:41 AM, Martijn Faassen wrote:
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. A
Martijn Faassen wrote:
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. Am I at all on the right track wit
On Wednesday 31 August 2005 05:41, Martijn Faassen wrote:
> Okay, this is clear. It's not that clear to me how to efficiently make a
> subscriber only handle one object type (I've been using the "is this a
> IFoo? If not, return" pattern at the start of subscribers), but that's
> another discussion
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. Am I at all on the right track with my
thinking on it?
I
Jim Fulton wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be missing
in zc.catalog. Am I at all on the right track with my thinking on it?
What information?
Sorry for being unclear. I meant the inf
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
...
It should be pointed out initially that the son-of-queued-catalog code
doesn't have anything to do with extents. I think Jim wants that
factored out when we have time so that can be a mix-and-match
capability.
Jim Fulton wrote:
Martijn Faassen wrote:
...
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be missing
in zc.catalog. Am I at all on the right track with my thinking on it?
What information?
Never mind. I m
Martijn Faassen wrote:
Jim Fulton wrote:
Martijn Faassen wrote:
...
In general, I'd like the catalog to remain fairly small and free of
logic.
I wanted to say this in the other thread you started on cataloging, but
didn't get to it. Ideally, a catalog wouldn't have any query logic
at all.
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
> ). I also think however that it's the wrong
place the ask for this information, as this doesn't work with the
extentcatalog.
Well, it depends on what you meant by "indexed" above.
Jim Fulton wrote:
Martijn Faassen wrote:
[snip]
> ). I also think however that it's the wrong
place the ask for this information, as this doesn't work with the
extentcatalog.
Well, it depends on what you meant by "indexed" above. Different indexes
index different objects. The extent ca
Martijn Faassen wrote:
Hi there,
Now that there's a plain catalog and an extent catalog, and while I was
implementing a 'not' operator for a query language, I ran into some
missing abstraction that would be convienient; a way to get all the
object ids that are indexed,
For some definition o
Hi there,
Now that there's a plain catalog and an extent catalog, and while I was
implementing a 'not' operator for a query language, I ran into some
missing abstraction that would be convienient; a way to get all the
object ids that are indexed, preferably in the form of a IFBTree so I
can d
13 matches
Mail list logo
