[Mulgara-dev] CRITICAL: Bug fix to Backup operation

[Ben Hysell]

Andrae,

We restore to a brand new Mulgara instance that has an empty server1
directory.

-ben

-----Original Message-----
From: mulgara-dev-bounces at mulgara.org
[mailto:mulgara-dev-bounces at mulgara.org] On Behalf Of Andrae Muys
Sent: Wednesday, March 26, 2008 9:29 PM
To: Mulgara Developers
Subject: Re: [Mulgara-dev] CRITICAL: Bug fix to Backup operation


On 26/03/2008, at 11:48 PM, Ben Hysell wrote:
>>> 2. Read through the string pool looking for any entries that start
> with _node followed by a number
>
>> As discussed below, this step should *never* happen - even if you  
>> *are*
> using blank-nodes.
>
> But if a backup has node numbers in the triples section and not in the
> string pool and we restore that backup and then query it the query  
> will
> return "_node######".  If you then backup that Mulgara and look in the
> string pool you'll then find: ## "_node######".

That suggests that somewhere in the backup/restore process a blank- 
node has been converted into a literal.  I have just tried to  
reproduce this on a clean image, and haven't been able to do it - so  
all I can suggest is that this is happening as a side-effect of other  
weirdness we are seeing.

Can I ask if you are restoring to the original mulgara instance?  Or  
to a new one?

Andrae

-- 
Andrae Muys
andrae at netymon.com
Senior RDF/SemanticWeb Consultant
Netymon Pty Ltd


_______________________________________________
Mulgara-dev mailing list
Mulgara-dev at mulgara.org
http://mulgara.org/mailman/listinfo/mulgara-dev