Just another information.
While debugging I noticed that in the correct case, the children class comes first in the "for" iteration. First ServicoEnderecoEmail appears, then Servico, then Habilitavel.
When I add another Servico child class, Servico comes BEFORE the ServicoEnderecoEmail class in the "for" iteration, resulting in a wrong tableRegistry dictionary.
I don't know if the problem is in this part or in the registry construction.
The problem is in class InheritableSelectResults, on __init__ method, on the second "for registryClass in allClasses".
When there's just 21 classes in registry, the tableRegistry dictionary has, after the "for" execution, the Habilitavel class (which is the class that derivate from InheritableSQLObject) and the ServicoEnderecoEmail class.
When I declare another class, any one, that inherits from Servico, the tableRegistry dictionary has after the "for" execution, Servico and ServicoEnderecoEmail.
I didn't understand the code too much. I'll study it a little more to try to undestrand it.2006/10/13, Oleg Broytmann <firstname.lastname@example.org>:On Thu, Oct 12, 2006 at 04:49:01PM -0300, Raphael Derosso Pereira wrote:
> class ServicoEGW(Servico):
> """Just this triggers the error"""
> If I change to:
> from csi.entidades.servico import *
> class ServicoEGW:
> """This doesn't trigger the error"""
But what is class ServicoEGW? It was mentioned anywhere. Can you produce
a short program that demonstrates the problem so I can investigate?
Oleg Broytmann http://phd.pp.ru/ email@example.com
Programmers don't die, they just GOSUB without RETURN.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
sqlobject-discuss mailing list
Raphael Derosso Pereira
Engenheiro da Computação
Phone: +55 41 3024-7430
Cel: +55 41 9661-4442