gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] jl-gui et alii - v_emr_tree


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] jl-gui et alii - v_emr_tree
Date: Mon, 26 Aug 2013 21:34:21 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, Aug 24, 2013 at 10:22:37PM +0200, Jerzy Luszawski wrote:

> > > > 2) Do you see problems with rewriting the view to
> > > >    directly look at the base tables rather than
> > > >    views thereof ? (that way this view will be more
> > > >    robust when other views are modified)
> > > AFAIK Postgres does good job by optimizing the views by itself.
> > > Moreover it would probably require more nested SELECTS, exactly as the
> > > base views do. I see no benefits (except getting independence from
> > > other views, but in exchange for readability).
> > 
> > I see, yes, readability suffers a bit when looking directly
> > at the base tables. I did not mean using per-column nested
> > SELECTs, however (which I agree are not the best solution),
> > but rather joining against the base tables.
> 
> For now I would rather leave this view as is because it worked for me
> for long time, so I can assure everyone that everything based on it
> will work.

I can see this argument.

> I will incorporate your suggestion from below and spend some
> time with it for testing.

Great. In the mid-term I'd really recommend getting rid of
looking at other views rather than base tables because that
way I won't break your view when I might change the views
your view looks at ;-)

> What is the planned release date of future
> database version?

Together with the next version :-)

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]