gnumed-devel
[Top][All Lists]
Advanced

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

[Gnumed-devel] feedback re business/gmOrganisation.py


From: sjtan
Subject: [Gnumed-devel] feedback re business/gmOrganisation.py
Date: Mon, 24 May 2004 01:38:17 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

The draft code was "re-factored" so that multiple org objects can be constructed with 4 calls:
e.g. first call , get the ids with an sql select of desired org objects.
second call, get the comm_channel info for those ids, and organize by org_id,
and third call get the address info for those ids , and organize by org_id.
This allows "findOrgsBy...( )" aggregate functions to reduce the number of sql calls. Begs the question why not just use a massive select like Richard's original contacts example posted, as that just requires query processing in the backend and one sql call. SQL rules again? O-O is just a plot to foist network databases on us all again?





reply via email to

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