ilson@msh.org
I am not sure the restrictions on the user tables make much sense really. I=
think we should consider removing them=2Cas they are easily circumvented.=
=20
=0A=
Several approaches are possible as Randy outlines. Just to emphasize...
=0A=
=20
=0A=
1) Encapsulation of the view in a function . This helps to circumvent the i=
ssues Randy outlines with direct views on the database. This could be coupl=
ed to a cron job to materialize the result set to a CSV file which could be=
linked to a resource. A function would allow you to create an SQL view as =
DHIS would not know what is going on inside the function.=20
=0A=
=0A=
2) Using a JDBC source and feeding this into a report.
=0A=
(2) is probably the simplest approach.=20
=0A=
This will only give you the last login however. If you want to knows who lo=
gs on frequently however=2Cyou would probably need to perform a more detail=
ed analysis of the logs.=20
=0A=
Regards=2C
=0A=
Jason
=0A=
--Sent from my mobile
=0A=
ยทยทยท
On Sep 6=2C 2013 7:10 PM=2C "Gomez Phiri" <gomezphiri@hotmail.com> wrote:
=0A=
=0A=
=0A=
=0A=
Hi Wilson=2C
I have pgadmin access and I can run all the queries from there=2C I just wa=
nted to create the view for some non technical users who cannot query the d=
atabase for user activity directly through pgadmin.=0A=
Thanks
Gomez.