dhis2-users team mailing list archive

[Halvdan Hoem Grelland <halvdan@xxxxxxxxx>]

Hi,

1) The SQLView feature is basically just a convenient way to expose the
database directly, meaning you query the database tables with straight SQL
statements. Unfortunately there's no documentation detailing names of
tables and columns in the DB, so you'll have to look them up in an instance
of a DHIS2 db yourself. PgAdmin III or similar are good tools to do so (if
using postgres).

In any case, you'll find that most names are fairly self-explanatory. For
example: DataElement is found in the dataelement table, which has a
dataelementid, a uid, a name, a shortname and so forth.

2) In the web api we expose the "id" of datasets (or any object for that
matter), which is really the "uid" in the database. You can query the api
for the id, and then run queries against the uid column of any object using
these.

For example to fetch the name and uid of all dataSets you would do
https://play.dhis2.org/dev/api/dataSets.json?fields=name,id&paging=false

On Thu, Aug 25, 2016 at 1:21 PM, Hinds, Ms. Angela (CAR) <
hindsang@xxxxxxxxxx> wrote:

> Hi
>
>
>
> I have not used the SQL view before and after perusing the documentation,
> I am still not clear on
>
> 1.       Which name references are to be used in the SQL statement for
> the elements and table?  My current element names and short names used by
> the forms have spaces
>
> 2.       Using the web.api how do I get a list of the relevant reference
> names to use for the particular dataset
>
>
>
> Regards,
>
>
>
> Thank you.
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Halvdan Hoem Grelland
Software developer, DHIS 2
University of Oslo
http://www.dhis2.org <https://www.dhis2.org/>