On Tue, 2003-10-07 at 16:57, Chris McDonough wrote:
> OK, I checked in changes on the 2.6, 2.7, and HEAD branches that add an
> update_metadata keyword argument to Catalog's catalogObject and
> ZCatalog's catalog_object. The argument defaults to true. I also added
> some tests, and made sure tha
OK, I checked in changes on the 2.6, 2.7, and HEAD branches that add an
update_metadata keyword argument to Catalog's catalogObject and
ZCatalog's catalog_object. The argument defaults to true. I also added
some tests, and made sure that the reindexIndex method of ZCatalog took
advantage of this
On Tue, 2003-10-07 at 09:52, Casey Duncan wrote:
> This is broken in 2.6.2 and I would consider it a bug in that release. I would
> support an improved api such as:
>
> catalog_object(obj, idxs=[], metadata=1)
>
> The way it is currently breaks at least one of my applications as well
> (ironica
On Tuesday 07 October 2003 12:08 pm, Chris McDonough wrote:
> On Tue, 2003-10-07 at 09:52, Casey Duncan wrote:
> > This is broken in 2.6.2 and I would consider it a bug in that release. I
would
> > support an improved api such as:
> >
> > catalog_object(obj, idxs=[], metadata=1)
> >
> > The way
On Tue, 2003-10-07 at 10:52, Casey Duncan wrote:
> This is broken in 2.6.2 and I would consider it a bug in that release. I would
> support an improved api such as:
>
> catalog_object(obj, idxs=[], metadata=1)
>
> The way it is currently breaks at least one of my applications as well
> (ironica
On Tuesday 07 October 2003 10:41 am, Yuppie wrote:
> Hi!
>
>
> Casey Duncan wrote:
> > This is broken in 2.6.2 and I would consider it a bug in that release. I
would
> > support an improved api such as:
> >
> > catalog_object(obj, idxs=[], metadata=1)
>
> I'm sure you mean catalog_object(obj,
Hi!
Casey Duncan wrote:
This is broken in 2.6.2 and I would consider it a bug in that release. I would
support an improved api such as:
catalog_object(obj, idxs=[], metadata=1)
I'm sure you mean catalog_object(obj, uid, idxs=[], metadata=1) if we
are talking about the ZCatalog interface.
I am
This is broken in 2.6.2 and I would consider it a bug in that release. I would
support an improved api such as:
catalog_object(obj, idxs=[], metadata=1)
The way it is currently breaks at least one of my applications as well
(ironically, this was an application the Chris was also working on).
I
Thanks for your note.
Yes, version 0.9 went out with some silly bugs, and I haven't had time
to fix them.
However, we now have a customer funding some Zope-related work, so I
imagine I will have time to work on CVSFile again within 3-6 weeks.
CVSFile will be supported until it gets replaced by a
Hi!
Chris McDonough wrote:
Option 1:
Add an update_metadata flag to the catalogObject method with a default
of True on all branches.
Option 2:
Do nothing, but add the "updateMetadata" method to the ZCatalog
interface.
Option 1 would only take effect when 2.6.3 was released (if ever) and
2
How does Zope handle Unicode encoding/decoding of non-UTF8 encodings?
I see encoding/decoding functions popping up in products (e.g.,
Archetypes), but I thought Zope already had this covered?
Bye,
--
Bjorn
___
Zope-Dev maillist - [EMAIL PROTECTED]
h
11 matches
Mail list logo
