Thanks for prompt reply, I had actually looked at the properties for that and all other tables with category/options in the name (in pgadmin), but it was showing with only 1 records. Had to actually open the table to see the options, so I guess postgresql don’t automatically update it’s meta-data tables with accurate record counts. Lesson learnt…
Regards
Calle
···
On 13 February 2018 at 11:40, Morten Olav Hansen morten@dhis2.org wrote:
Sure Calle, I guess postgres must defend itself from the likes of us
···
On 13 February 2018 at 09:48, Calle Hedberg <calle.hedberg@gmail.com> wrote:
Morten
Thanks for prompt reply, I had actually looked at the properties for that
and all other tables with category/options in the name (in pgadmin), but it
was showing with only 1 records. Had to actually open the table to see the
options, so I guess postgresql don't automatically update it's meta-data
tables with accurate record counts. Lesson learnt...
Regards
Calle
On 13 February 2018 at 11:40, Morten Olav Hansen <morten@dhis2.org> wrote:
dataelementcategoryoption
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo http://www.dhis2.org
On Tue, Feb 13, 2018 at 4:38 PM, Calle Hedberg <calle.hedberg@gmail.com> >> wrote:
Hi
Quick question: I have just added two CATEGORY OPTIONS to an instance -
but in which table in the database are those options stored?