Re: [SQLObject] Hello and Connections (to start)

[Ian B. <ia...@co...>]

I'm not going to get too stressed out about a single unused dictionary
and threading lock per application :)  Per SQLObject instance, that
would be a problem.

On Wed, 2003-03-12 at 21:47, Luke Opperman wrote:
> There was a semi-decent reason conscious decision not to call parent's init:
> It's in the parent's init that the pooling info is created. But I suppose that's
> a smaller price to pay than having things break in the future. I guess my only
> other thing is that if you agree this is about the way to do this sort of
> override, that DBAPI's __init__ should be careful about creating too much
> overhead. :)
> 
> - Luke
> 
> Quoting Ian Bicking <ia...@co...>:
> 
> > This looks like the right way to go about this.  You should call the
> > parent __init__, though.  More like:
> > 
> > def __init__(dsn, debug=0):
> >     PostgresConnection.__init__(dsn, debug=debug)
> > 
> > Though you don't *really* have to override __init__ at all, except if
> > you want to disallow non-applicable init arguments.
> > 
> >   Ian
> > 
> > 
> > 
> 
> 
>