my current task is to establish a connection to reporting and to get information from it (from C++ side).

When we use the Services API we can GET information from reporting through a CSV file, like mentioned here: https://forum.innovaphone.com/moodle2/mod/forum/discuss.php?d=26614

What if we want to access the information by firing own (readonly) SQL commands onto the reporting db:

- From wiki: http://wiki.innovaphone.com/index.php?title=Reference13r1:Concept_App_Service_Reporting

-> "You hand the Reporting database credentials to your own App and connect directly to the Reporting database within your own App. This saves you the parsing and storing of the data, but you must maintain your queries if something in the Reporting database is changed. It is important, that you should just access this data readonly and that you do not modify table data"

- So there is no way to receive reporting database credentials through the pbx? or another way? do i miss something?

- If there is no possibility to get reporting database credentials through pbx, then the following solution takes affect :? Our app needs some kind of configuration option where we write/store the reporting database password/credentials and use it to access the reporting db from our app

- We need to change the default reporting db password so that we know the current one, right?

In the next step, do we need a second IDatabase Object on our C++ side, right?

#: this->repodatabase = service->databaseProvider->CreateDatabase(iomux, this, this);

#: this->database = service->databaseProvider->CreateDatabase(iomux, this, this);

#: this->database->Connect(args->dbHost, args->dbName, args->dbUser, args->dbPassword);

#: this->repodatabase->Connect(configrepo->dbHost, configrepo->dbName, configrepo->dbUser, configrepo->dbPassword);

- Is there anything I need to consider before accessing this second database from our app instance? grant access to anything or something else?

Best regards

Mladen

(Trying to anticipate what all might come my way. And to get a feeling for the time estimate before starting with the implementation)