Re: [bdbxml] getAllDocuments

I can wait for 2.2.

I'm also seeing a bug with unique indexes keeping stale values when I use 
node-indexed node storage containers.  I don't have the same problem with 
non-node-index node storage or wholedoc storage containers.  If you are 
unaware of such problems, I can provide more information, though this is 
more complicated.  I suspect you've already seen this though.

Michael

On Fri, 29 Jul 2005, George Feinberg wrote:

>
> Michael,
>
> Thanks.  This is, in fact the flags bug I mentioned.  It will be fixed in 
> release
> 2.2.  If you really need a patch, it may be possible, but it's
> a bit complicated.
>
> There is no workaround in user code other than not using
> that flag.
>
> Regards,
>
> George
>
> On Jul 29, 2005, at 10:31 AM, Michael Allman wrote:
>
>> I just reran the test case.  It turns out my memory is slightly crusty. 
>> Here's the real deal:
>> 
>> The exception is thrown from the 
>> com.sleepycat.dbxml.dbxml_javaJNI.XmlValue_asString__SWIG_0() native 
>> method, not getAllDocuments().  However, I see this exception when I call 
>> xmlResults.next().asString() where xmlResults = 
>> xmlContainer.getAllDocuments(txn, documentConfig) where the documentConfig 
>> is set for LockMode.RMW.  Again, this only happens to me when I use a node 
>> storage container.  If I rebuild the container with wholedoc storage --- no 
>> problemo.  BTW, if it's relevant, I am passing a transaction to 
>> getAllDocuments().
>> 
>> Here's the relevant stack trace snippet:
>> 
>> Caused by: com.sleepycat.dbxml.XmlException: Db::cursor: Invalid argument, 
>> errcode = DATABASE_ERROR
>>     at com.sleepycat.dbxml.dbxml_javaJNI.XmlValue_asString__SWIG_0(Native 
>> Method)
>>     at com.sleepycat.dbxml.XmlValue.asString(XmlValue.java:105)
>> 
>> Thanks a lot.
>> 
>> Michael
>> 
>


------------------------------------------
To remove yourself from this list, send an
email to [email protected]