[Mulgara-dev] org.mulgara.resolver.spi.LocalizeException: Unable to localize

[Paul Gearon]

Hi Pradeep,

I suspect that the backup/restore is unrelated, but I'd like to
eliminate that possibility.

Can you export the model to a file, and then load it up into a fresh
system that you then execute the query against? I'm expecting the
behavior will not change, though if it does then it tells us that the
problem is in the backup/restore.

Incidentally, how many items are being returned from the outer WHERE clause:
  $a <rdf:type> <topaz:Article> and $a <topaz:nextObject> $f;

Is is possible to go through these with a Java loop and run the
subquery with a fixed value rather than "$a"? I'm not suggesting this
as a fix for your problem. It's just that my first thought is that the
transaction is somehow not being passed down to the subquery.

Regards,
Paul

On Wed, Jul 2, 2008 at 6:58 PM, Pradeep Krishnan
<pradeepk at soft-point.com> wrote:
> Pradeep Krishnan wrote:
>>
>> Hi Paul,
>>
>> We are getting this exception while executing the following query:
>>
>> select $a $f subquery ( select $s <topaz:nextObject> $o from
>> <local:///topazproject#ri> where $s <topaz:nextObject> $o and $a
>> <dcterms:hasPart> $s) from <local:///topazproject#ri> where $a <rdf:type>
>> <topaz:Article> and $a <topaz:nextObject> $f;
>
> Oops. Cut paste error. The query is only executed once.
>
> This was a full backup and restore using:
>
> backup <local:///topazproject> to <file:/tmp/serverbackup.gz>;
>
> and:
>
> restore <local:///topazproject> from <file:/tmp/serverbackup.gz>;
>
> Cheers,
> Pradeep
>