R. David Murray writes:
...
The issue is that parts of the database get updated periodically from an
external source. That is, the author and book tables get replaced
wholesale. But the Book and Author objects are cataloged using
ZCatalog, doing a full text index on a combination of
I've got an analogous but different problem with ZCatalog udpates. I'd
like to ask for ideas about the best way to handle this.
I've got a ZPatterns based ap that is pulling data from a postgresql
database. But associated with the object created out of the database
are signficant chunks of
[Chris McDonough]
| Note that the algoritm is simple - for each index, compare the what exists
| in the index to what is to be put in. If they're the same, do nothing. If
| they're different, reindex. I wasn't able to understand completely from
| your description whether the object method
On Sat, 3 Mar 2001, Chris McDonough wrote:
Has the physical path of the object changed? If not, the newer (2.3.0 + )
Nope.
catalog stuff should be smart enough to figure out whether anything inside
the object has changed during catalog_object. If nothing has changed, none
of the indexes
Cool. Now, in the examples I've seen for interfacing ZCatalog and
ZPatterns, the 'object updated' code does an unindex of the object
and then an index of the object. I copied that pattern for my
"the tables have been updated, reindex everything" code.
So what I should do instead is just do
Will the new data be 'made ready for indexing' before it is compared to
the
existing data? That is, will ZCatalog have to compute the data in some
way before it compares it to what is already stored?
Yes.
I'm wondering because it would be significant overhead to 'make a data
field
of
[Casey Duncan]
| Actually what I wrote assumes you are passing a Catalog not a ZCatalog.
| So you will need to change it for a ZCatalog to:
I figured that out. :-)
There is one problem, the uids stored in the Catalog are based on the path of the
object, so I guess I'll have to make a copy of
Casey Duncan wrote:
"Morten W. Petersen" wrote:
Hi guys,
I've got a problem with ZCatalog. I've got plenty of large
objects, ranging from 100KB to 100MB in size. Needless to
say, these take up a lot of processor time when indexed by
the ZCatalog.
Now, these object have to