Re: Fwd: Re: [Gnumed-devel] Questions About GNUmed DataBase

[Karsten Hilbert]

> > > Thanks for your time and effort, by this way you have mentioned we
> think
> > > this will caused lots of data redundancy
> >
> > Why do you think that ?
> >
> > What are you referring to by "this" ?
> >
> > > and would effect on performance of database if we want to check the
> > > constrains, is it true or not?
> >
> 
> As long as the query is joining on indexed values, then performance should
> not be a problem. Unless the redundant data needs to be maintained ...

Hint: there is nearly no redundant data in the GNUmed database schema
(that I know of) - I am trying to make them *think* - after all, it's
a database *class* ...  ;-)

> causing
> a) multiple queries to update and b) a maintenance nightmare. I don't know
> the GNUMed db schema to comment if this is the case. Sometimes you need to
> index the index if the data grows quite large.

I don't think PostgreSQL supports that as a builtin. GNUmed likely
won't need it either.

> I've never performed SVT on GNUMed, but it would be a worthwhile exercise
> if
> you would like to try. Load up the DB with lots of data and try running
> some
> scenarios.  Has anyone performed SVT on GNUMed in the past? What were the
> results like?

The one thing I did test back in the days (64 MB RAM, PG 7.1) was to
search for a patient among about 150k records. That was
near instantaneous.


Karasten
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01