Hello Catrina; I'm not entirely clear on what you mean by "immediately available", but I think some explanation will help. When you specify a text serialization in a script, it loads the entire file into memory. If you open a connector (to a back-end such as Oracle, etc.), a script will open the connection then wait for a query to bring data into memory. Composer works this way as well, except that it caches some triples for displaying the UI.
So the next script module will bring the requested triples into memory. -- Scott On Dec 10, 10:27 am, Catrina <[email protected]> wrote: > I have a SPARQLMotion script that outputs some RDF into Oracle. My > script then creates a .oracle file to connect to the rdf in Oracle. > Similar to the .oracle files that are manually created from Composer > through File -> New -> RDF/OWL Oracle Database Connection. I added > something to my script to programmatically create the .oracle file. > > I run my script from TopBraid Live, but the rdf from the .oracle file > is not readily available. However, if I output my rdf into an .n3 > file, the file is readily available. Is it possible to make > the .oracle rdf readily available programmatically without affecting > other user sessions in TopBraid Live? > > Thanks, > Catrina -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
