t;
>
>
> - Original Message
> From: "joha...@ifi.uio.no"
> To: Murodullo Latifov
> Cc: Knut Staring ; dhis2-devs@lists.launchpad.net
> Sent: Tuesday, June 9, 2009 3:55:37 PM
> Subject: Re: [Dhis2-devs] Global ranges
>
>>
>> Hi,
>>
>&
age
From: "joha...@ifi.uio.no"
To: Murodullo Latifov
Cc: Knut Staring ; dhis2-devs@lists.launchpad.net
Sent: Tuesday, June 9, 2009 3:55:37 PM
Subject: Re: [Dhis2-devs] Global ranges
>
> Hi,
>
> Most likely this is pg security restriction. Open PGadmin and navigate to
> mi
sts.launchpad.net
> Sent: Monday, June 8, 2009 10:51:06 PM
> Subject: Re: [Dhis2-devs] Global ranges
>
> After running the below statement and trying to access Data Entry, we get
> this error. Any ideas about what causes the "ERROR: permi
"
To: Knut Staring
Cc: dhis2-devs@lists.launchpad.net
Sent: Monday, June 8, 2009 10:51:06 PM
Subject: Re: [Dhis2-devs] Global ranges
After running the below statement and trying to access Data Entry, we get
this error. Any ideas about what causes the "ERROR: permission deni
After running the below statement and trying to access Data Entry, we get
this error. Any ideas about what causes the "ERROR: permission denied for
relation minmaxdataelement"?
[+] Exception (org.hibernate.exception.SQLGrammarException): could not
execute query
*
org.hibernate.exception.SQL
Ok, I think I would like to recommend ignoring the file I sent and rather
redefine the table and then run Thanh's first SQL, for a total of three
statements. They can all be run in one go, just paste the following into the
SQL window in PgAdmin III:
DROP TABLE minmaxdataelement;
CREATE TABLE minm
On Wed, May 20, 2009 at 3:57 AM, Ngoc Thanh Nguyen <
thanh.hispviet...@gmail.com> wrote:
>
>
> - if you want all dataelements have ranges
>
> insert into minmaxdataelement(sourceid, dataelementid, minvalue, maxvalue)
> select organisationunitid, dataelementid, 0, 99 from organisationunit,
> datael
On Wed, May 20, 2009 at 3:13 AM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> Would like to hear what the devs have to say, but maybe something like...
>
> 1) Delete the primary key minmaxdataelementid
> 2) Execute
>
> INSERT INTO minmaxdataelement
> SELECT a.organisationunitid, b.datae
Would like to hear what the devs have to say, but maybe something like...
1) Delete the primary key minmaxdataelementid
2) Execute
INSERT INTO minmaxdataelement
SELECT a.organisationunitid, b.dataelementid, 0 as minvalue, 99 as
maxvalue, 'TRUE'::boolean as generated
FROM (SELECT DISTINCT organisa
Hi again, I'm assuming the orgunit and dataelement IDs are the same as in
our SL demo (http://208.76.222.114/dhis_sl). This is a big assumption, but
anyway your db will suffer no harm if it's not the fully the case.
Right click on the following link and save the file, then unzip it somwhere
and ma
Basically, you need to add rows to the minmaxdataelement tabls, which means
a bunch of INSERT statements. I can try to generate it.
Knut
On Tue, May 19, 2009 at 5:06 PM, wrote:
> Hi,
>
> In Sierra Leone, none of the orgunits have defined min-max ranges yet, and
> the historical data is too poor
Hi,
In Sierra Leone, none of the orgunits have defined min-max ranges yet, and
the historical data is too poor to be used for calculation of such ranges
yet. Still, there have been some instances of really bad typos, such as
775 instead of 75. Most entries (maybe around 98%) are below 100, so as a
12 matches
Mail list logo
