Re: [Gnumed-devel] freshly-created patients do not populate the 'recent searches' dropdown

[Karsten Hilbert]

On Fri, Dec 02, 2011 at 09:14:48AM +0000, Jim Busser wrote:

> >> Otherwise it maybe needs to be achieved as a separate function or Report 
> >> stored query
> > 
> > The latter feels logical to me, although likely not really
> > particularly user friendly.
> 
> a few queries for consideration for I decided to forgo DISTINCT ON because 
> that precluded ORDER BY unless I would build a more complex query
> 
> -- encounters recently created or modified (by current user)
> 
> select to_char(c_e.modified_when,'yyyy.mm.dd hh:mm') modified, d_n.lastnames 
> || ', ' || d_n.firstnames person_encountered, c_e.fk_patient pk_patient, 
> c_e.assessment_of_encounter aoe
> from  clin.encounter c_e
> inner join dem.names d_n
> on c_e.fk_patient = d_n.id_identity
> where c_e.modified_by = "current_user"()
> order by modified_when desc ;
> 
> -- encounters recently created or modified (by any user)
> 
> select to_char(c_e.modified_when,'yyyy.mm.dd hh:mm') modified, 
> c_e.modified_by by_user, d_n.lastnames || ', ' || d_n.firstnames 
> person_encountered, c_e.fk_patient pk_patient, c_e.assessment_of_encounter aoe
> from  clin.encounter c_e
> inner join dem.names d_n
> on c_e.fk_patient = d_n.id_identity
> order by modified_when desc ;

Added.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346