Jeff, we aim at the next TBS generation for February/March. We can do nightly builds before that and share them with you. But these won't have the same amount of QA on them.
Regards, Holger On Dec 8, 2009, at 12:38 PM, Schmitz, Jeffrey A wrote: > In the meantime you may need to use the default graph. > > Don't think that's an option. Our app manages MANY models at the same time, > and that's not going to change. Any guess on when support will be added? > I'd really like to make the transition to SDB ASAP since we're going to have > a new customer early next year. Would rather start them on SDB than have to > start on them on RDB and then transition them to SDB. > > Jeff > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Holger > Knublauch > Sent: Tuesday, December 08, 2009 2:26 PM > To: [email protected] > Subject: Re: [tbc-users] Anyone using Jena RDB database? > > Hi Jeff, > > indeed we are not supporting the named graphs of SDB yet. We are actually > working this as we speak. The code currently calls > > return new GraphSDB(store) { > > to create the GraphSDB. I guess we will add another property to the SM module > (and thus to the .sdb file) to specify the graph name (or just use the > declared base URI). We'll keep you posted. In the meantime you may need to > use the default graph. > > Holger > > > On Dec 8, 2009, at 11:03 AM, Schmitz, Jeffrey A wrote: > >> After looking at what's going on in MySQL (using MySQL Query Browser), it >> looks like TBC may always be trying to find the specified model at the >> default model location, instead of the named model that I specify in the SDB >> dialog. Is there some option to tell it to look for a named model, not the >> default model in the SDB database? >> >> i.e. it looks like it's using >> >> SDBFactory.connectDefaultModel >> >> Instead of >> >> SDBFactory.connectNamedModel >> >> That's just a guess based on the fact that in the prefixes table, the ':' >> prefix uri always changes to whatever the last model URI I tried to connect >> to using TBC. I'm assuming the ':' prefix represents the default model >> prefix. >> >> Jeff >> Work: 314-232-1997 >> Cell: 636-448-5990 >> >> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On >>> Behalf Of Schmitz, Jeffrey A >>> Sent: Tuesday, December 08, 2009 12:48 PM >>> To: [email protected] >>> Subject: RE: [tbc-users] Anyone using Jena RDB database? >>> >>> Just noticed this after upgrading to the latest TBC. I'm >>> moving to using the SDB database, and have actually got it >>> working with our app (although SPARQL queries are MUCH slower >>> right now), but I still can't create a SDB model in TBC that >>> will connect to existing SDB models in my MySQL database. >>> When I create a model I get no errors, but it shows the model >>> being empty when it's not. Are there any tricks to creating >>> an SDB model? What about specification of layout? >>> >>> Jeff >>> >>> >>> >>>> -----Original Message----- >>>> From: Holger Knublauch [mailto:[email protected]] >>>> Sent: Monday, August 03, 2009 3:37 PM >>>> To: [email protected] >>>> Subject: [tbc-users] Anyone using Jena RDB database? >>>> >>>> >>>> Dear users, >>>> >>>> TopBraid has been supporting the "old" Jena RDB database for many >>>> years now, but with 3.1 we have also started to support the next >>>> generation of RDB, called SDB. In order to simplify maintenance and >>>> reduce the number of TopBraid plugins, we are considering >>> to drop RDB >>>> support from the next major release (3.2). >>>> >>>> For those users still using RDB, we recommend upgrading to SDB if >>>> possible. If this is impossible for you, please contact me >>> and we can >>>> discuss continuing RDB support for longer. >>>> >>>> Thanks, >>>> Holger >>>> >>>> >>>> --~--~---------~--~----~------------~-------~--~----~ >>>> 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 >>>> -~----------~----~----~----~------~----~------~--~--- >>>> >>>> >>> >>> -- >>> >>> 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. >>> >>> >>> >> >> -- >> >> 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. >> >> > > > -- > > 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. > > -- > > 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. -- 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.
