Hi,

Besides was Joost said so far...

Personally I don't like the fact of having a Config class that connects to a database and created a database handler... and even not talking about relying on some "magic" like the fact that use calls import while base does not...

Don't you think something is wrong in the design itself?

Why you don't have a Config class just for config purposes? Even the connection to the database can be in his own class or even in a base class for your model, so that it gets called via super... there are a few alternatives, but I really would leave Config for configuration, right now you think about connecting from it to a database, but it might be that later on, you think that it could be handy to _not_ connect to a database...

Resuming, think again about what you want to achieve, is there really any constraints of doing it the way you're thinking?

Regards,