On Fri, Dec 21, 2012 at 11:14 AM, Wilson,Randy wrote:
> Hi Lars and Jason,
>
> ** **
>
> I agree as well. Remember the views are actually crucial for custom
> iReports as well – so a mydatamart only solution is not sufficient. We
> have extended our system with tables to manage results bas
; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Help creating links to download materialized views
Hi Lars,
I could not agree with you more. I think the ability of users to extract out
chunks of data from the data mart based on indicator or data element groups
would largely solve this
Hi Lars,
I could not agree with you more. I think the ability of users to extract
out chunks of data from the data mart based on indicator or data element
groups would largely solve this problem of external views at least in
Rwanda. It is a great idea, and hope it can be implemented in future
relea
helpful. I’m not sure how we can
> get around the need to drop and rebuild these tables.
>
> ** **
>
> Randy
>
>
>
> ** **
>
> *From:* Lars Helge Øverland [mailto:larshe...@gmail.com]
> *Sent:* Thursday, December 20, 2012 10:51 PM
> *To:* Jason
on,Randy; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Help creating links to download materialized views
Okay. So with materialized view you are referring to a plain db table, right? I
thought you meant creating a view with sql something like "create materialized
view" b
On Fri, Dec 21, 2012 at 5:47 AM, Jason Pickering <
jason.p.picker...@gmail.com> wrote:
> Yes, in this context, a materialized view is simply a table which is
> produced from an SQL view. The advantage of course is that materialized
> views can be indexed, etc and are normally much faster to serve
Yes, in this context, a materialized view is simply a table which is
produced from an SQL view. The advantage of course is that materialized
views can be indexed, etc and are normally much faster to serve than
dynamic SQL views.
The one thing I did not mention, is the refreshment of the materializ
Okay. So with materialized view you are referring to a plain db table,
right? I thought you meant creating a view with sql something like "create
materialized view" but I can see that has not been implemented directly in
postgres yet.
Anyway I think creating a dhis sql view per table is a reasonab
Just to add to the grab bag, making the resource tables themselves
available as csv or what have you would be an alternative to reconstructing
them from the xml metadata export that we do currently in mydatamart.
Jason has suggested this to me on occasion. I have now got a high speed
dxf1 metadat
Hi Randy and Lars,
The fundemental problem is that view which they were using are linked to
the resource tables. These tables need to be regenerated, and when they are
regenerated, the tables are dropped and recreated. If views are linked to
these tables, the resource table regeneration cannot take
Hi Randy,
let me see if I get you correctly: The problem is mainly that you cannot
drop your sql views in an arbitrary order since they depend on each
other? Also, your views do not depend on any dhis resource table, and you
completely maintain your views through the cron job.
Assuming this, woul
In Rwanda we have found report tables and MyDatamart inadequate for the needs
of many of the central level health programs. What they want is a dump of all
the datavalues in specific dataelement and indicator groups along with the
related orgunit hierarchy. We originally were doing this using
12 matches
Mail list logo
