|
From: Rob V. <rv...@vd...> - 2010-06-21 13:22:25
|
The exact behaviour of SaveGraph() with regards to how it affects an existing Graph of the same URI is left up to the implementer as it may be very dependent on the underlying store. The XML comments for the interface state that implementations should note their exact behaviour in the comments for the SaveGraph() method. This is typically stated in the remarks section rather than in the method summary though I'll make sure that methods clearly state this in their summaries from now on. I have updated all the comments on the existing implementations as of revision 789 Will also update online documentation shortly to highlight this Rob ---------------------------------------- From: Michael Friis <fr...@gm...> Sent: Monday, June 21, 2010 11:52 AM To: rv...@vd... Subject: Re: Updating/inserting-into DB-backed graph without doing LoadGraph > Do NOT use the SaveGraph() method as that typically overwrites any existing > Graph completely rather than merging with it (this is the behaviour for > Virtuoso) Great, that likely explains a lot of weirdness. Maybe that method should have a warning sticker, either in the online docs or in the intellisense comments... Michael -- http://friism.com (+45) 27122799 Sapere aude |