Absalom,
You have installed postgis with pg 9.5.4?
Regards
Calle
On 22 October 2016 at 10:36, Absolom MURAMIRA wrote:
> Dear All,
>
> I am testing release 2.25 and appreciate the developers' contribution to
> the good improvements to the DHIS2 application.
> Most of the
Dear Calle,
I installed postgis 9.5.3. Would that be the reason?
Sent from Yahoo Mail on Android
On Mon, 24 Oct, 2016 at 0:35, Calle Hedberg wrote:
Absalom,
You have installed postgis with pg 9.5.4?
RegardsCalle
On 22 October 2016 at 10:36, Absolom MURAMIRA
Hi Sam
This is caused by the metadata having some issues I'm guessing... I would
try and have a look at the network panel (in the web inspector) to see
exactly which request it stops on.. since you are using Chrome, you should
be able to right click on the console and select "log XHR requests",
On Tue, Oct 18, 2016 at 11:51 PM, Lorill Crees wrote:
> I see this blueprint was completed in 2.25 - great! Was this backported to
> 2.24? Is there documentation for this?
>
Yes, this is also in 224, docs are here:
>
>
>- *Return IDs of created items:* when we create a meta data (org unit,
>data element, etc), the API should return the newly created object id (or
>ids if multiple ones). Failed to do so require us to make a second call
>using a field to fetch the object back, this being a
Hi Lorill
So there's a couple of things to note here:
1) You probably want to use the name `me` instead of `currentUser` as it'
the new name for it (and has been for a while, just being aliased to
`currentUser``
2) In 224 we included a new `me` endpoint, which can now be reached at
`/api/24/me`
Hi Sam
We will have a better fix for 226, but for now you should be able to just
have name="default" on the elements (this will be nulled out during
validation phase, and then properly re-attach during import)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
Hi Jose
Lars will probably remember better.. but I think in 2.22 we had preheating
where all the object were loading in before the import started, so the
lookups would be very quick (but require more memory)
In later versions I think it now will try and "switch" over automagically..
but I don't
Hi Martin
I will forward you an email with a bit more details about the new format
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Tue, Oct 18, 2016 at 2:39 PM, Martin Van Aken
wrote:
> Hi !
> Good job with the release. By
Hi
Are you using chrome? could you open up the developer tools, and see if
there is anything in the console. Sounds like it can't load because of some
issues with your configuration.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, Oct 24, 2016 at
Hi Jose,
sure. If you can provide some context privately (server login, import file)
I can have a look. I should definitely not take that long.
best regards,
Lars
On Mon, Oct 24, 2016 at 4:36 AM, Morten Olav Hansen
wrote:
> Hi Jose
>
> Lars will probably remember better..
Dear Team, Thanks for all your suggestions.
Now the time of analytic is reduced to 10 hours 41 minutes.
We tried to VACUUM as Sam suggested but it didn't help then we upgraded
postgres from 9.4 to 9.5.4 and as Calle and Bob suggested we made some
changes in configuration file of postgres and it
Congratulation Neeraj and team ...it much appreciated
On Mon, Oct 24, 2016 at 11:08 AM, Neeraj Gupta
wrote:
> Dear Team, Thanks for all your suggestions.
>
> Now the time of analytic is reduced to 10 hours 41 minutes.
>
> We tried to VACUUM as Sam suggested but it didn't
13 matches
Mail list logo