logo       

Copy resource and collection bugs: msg#00046

text.xml.exist

Subject: Copy resource and collection bugs

Hi,

I can't get either copy resource or copy collection to work for me.

First, the NativeBroker.copyResource/3 method is broken, since it adds the
old document to the destination collection rather than the new one. (I'm
guessing this was never caught since the interactive client never changes
the document name while copying.) Once that's fixed, all kinds of things
break; for one, the new document isn't stored properly (no address is
assigned). I tried to fix that, but the new document still isn't indexed
properly; try any query on the copy and it will fail. (Changes mentioned
attached as patch, but more is needed, I just don't know what.)

As for copying collections, I can't get it to work at all. Starting from
a fresh database, I try to copy the system collection to a new spot (using
the client) and get stack traces from deep within the storage system.

Any help would be appreciated. It might be worth mentioning that I'm
running an embedded, local setup. Latest CVS version (with some local
patches, but hopefully in unrelated areas).

-- P.

--
Piotr Kaminski (piotr@xxxxxxxxxxxx)
It's the heart afraid of breaking that never learns to dance.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise