[Top][All Lists]

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

Re: [Gnumed-devel] address@hidden: Re: gmCfg dependancy on gmPG]

From: Hilmar Berger
Subject: Re: [Gnumed-devel] address@hidden: Re: gmCfg dependancy on gmPG]
Date: Thu, 26 Feb 2004 09:35:06 +0100

On Wed, 25 Feb 2004 21:53:37 +0100
Karsten Hilbert <address@hidden> wrote:

> ----- Forwarded message from Andreas Tille <address@hidden> -----
> > > Hilmar,
> > >
> > > does it make sense to move getFirstMatchingDBSet() into
> > > class gmCfgSQL ?
Well, one reason for having getFirstMatchingDBSet() was that you don't need to 
create a connection to the database first.This, in turn, is a requirement to 
initialize gmCfgSQL. So I would rather say no unless you auto-connect to the 
backend in gmCfgSQL.__init__(). 
> > > Else we'd need to add lazy import logic to them additionally
> > > to gmCfgSQL.__init__()
I guess that's the only possibility, then. I personally feel that splitting 
gmCfg in gmCfgFile and cmCfgSQL would be cleaner than adding all these "lazy 
import" code, but that may be a matter of taste.


reply via email to

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