Good pointer, Scott, thank you. I have to hack inside D2RQ to force it to see other users' schema. Please can you advise the correct way to temporarily deploy a new D2RQ jar file so that TBC-ME will work with it. A simple replacement of org.topbraidcomposer.d2rq_3.1.0.jar fools no-one (the relational import option does not appear)! BTW, the view here is that D2RQ will need a new command line parameter to pass through the Oracle username who owns the required schema. I'm just testing the principle by hard-coding it <eek>!
Peter On 22 Oct, 17:36, Scott Henninger <[email protected]> wrote: > Peter; If the query string doesn't allow setting internal_login, I'm > not sure what can be done. You can try editing the mapping set by the > D2RQ wizard. See the -Mapping.owl file, particularly the Database > instance. But it is not clear to me that D2RQ supports an internal > login. For more, seehttp://www4.wiwiss.fu-berlin.de/bizer/D2RQ/spec/ > > -- Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
