dhis2-users team mailing list archive

[David Muturi <dnmuturi@xxxxxxxxx>]

Hi Angela,
Its usually easier to write the queries using a copy of the database stored
locally and using the database access tools described above, test them
before copying them over to the SQL VIEW for front end access using dhis2,
one is able to easily troubleshoot any errors in the scripts and fix than
when using sql view directly.
rgds
David

2016-08-25 14:53 GMT+03:00 David Muturi <dnmuturi@xxxxxxxxx>:

> Hi Angela,
> You will need to access the database, ideally having a local copy on your
> laptop and using GUI tools i.e. Pgadmin, Navicat for PostgresSQl or other
> tools will allow you to access the backend. From there the names for the
> tables can serve as a guide e.g. datalement for dataelements, dataset for
> datasets, e.t.c For data, DHIS2 uses the "long and skinny" or EAV model so
> the dataelement,Source(orgunit),category (i.e. meta data) are stored
> together with  the data in the datavalues table.
> In case of any question regarding writing sql queries please free to get
> in touch with me.
> rgds
> David
>
> 2016-08-25 14:21 GMT+03:00 Hinds, Ms. Angela (CAR) <hindsang@xxxxxxxxxx>:
>
>> 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
>>
>>
>