Hi Holger, Actually, this problem originally occurred while working with 2.6. I upgraded to 3.0 beta1 to see if the error had already been fixed.
On Thu, Jan 29, 2009 at 7:46 PM, Holger Knublauch <[email protected]>wrote: > Hi Tim, > I hope you are aware of the fact that we have upgraded the AllegroGraph > drivers etc for 3.0 beta1, so you should make sure to have compatible > client/server versions. Also these changes have been made very recent, and > not everything may work smoothly yet. We will do further tests and keep you > posted, but for now I would recommend staying with TBC 2.6 for work on > AllegroGraph. > > Holger > > > On Jan 29, 2009, at 7:58 AM, Tim Harsch wrote: > > I forgot to mention: I'm on TBC 3.0 beta1 > > Thanks! > > On Wed, Jan 28, 2009 at 1:40 PM, Tim Harsch <[email protected]> wrote: > >> I think we are on the right track Scott. That is what I thought at first >> too. In fact after reading your reply I decided to repeat the process to >> make sure I didn't goof. As you can see from the following screen shot: >> http://screencast.com/t/U6iMWCfB >> >> All the indexes in the datastore were created aroun 11:17 this morning >> when I created the store outside TBC. I then tried the method I described >> earlier and this smashed all the non-index files, i.e. the mod times were >> updated. I did discover however that when I write a count query in SPARQL >> in TBC I get around 450 results. If I open the store with gruff I get the >> 130K triples I'm looking for. >> >> So, there are two databases, but... what am I doing wrong? I'm currently >> using AG 3.1.1. And I am putting this in the open dialog: >> http://screencast.com/t/AWPsDwxN >> >> >> On Wed, Jan 28, 2009 at 11:56 AM, Scott Henninger < >> [email protected]> wrote: >> >>> >>> Tim; The problem may be the name of the existing AllegroGraph >>> database name. To make it is being entered correctly, go to the >>> directory you are specifying in the wizard (AllegrpGraph directory) >>> and look at the file names. The name of the Allegro database will be >>> one of the folders, and it is case-specific. >>> >>> When not choosing Overwrite, Composer will make a connection file >>> only. But if the file doesn't exist, Composer will create one. >>> Therefore, what I suspect is happening is that Allegro is not finding >>> the file in the "AllegroGraph database name" wizard entry. Instead of >>> clobbering your datastore, it's just making a new one... >>> >>> -- Scott >>> >>> On Jan 28, 1:39 pm, Tim Harsch <[email protected]> wrote: >>> > Hi all, >>> > I am trying to open a pre-existing AG data store. I go to >>> > File->New->RDF/OWL Alelgrograph database. Provide the path of the >>> store and >>> > the database name, make sure to leave "Overwrite existing database" >>> > unchecked. It then creates the .allegro file and what not, but stomps >>> the >>> > original store. >>> > >>> > First, am I going about trying to open the store in the right way? >>> And, >>> > regardless, it seems if I don't check the overwrite option then it >>> should >>> > not overwrite... >>> > >>> > Thanks, >>> > Tim >>> >>> >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
