hi, i'm back to the cane field...

> do your ABC tests all use select_mapper ?   ticket 795 revealed
> that totally basic ABC loading was broken if you're using
> "secondary" loads of the remaining attributes (which is the default
> behavior when you dont specify select_mapper).
u mean mapper's select_table=..? it's allways used because of 
polymorphism.

today i tried those ABC things, found 2 issues:
 - r3449 introduces some memory leak 
 - r3646 introduces some forever-recursion, goes like:
  File "other/expression.py", line 355, in <module>
    p2 = session.query( Person).filter_by( name= 'pesho').first()
  File "/home/az/src/hor-trunk/sqlalchemy/orm/query.py", line 595, in 
first
    ret = list(self[0:1])
  File "/home/az/src/hor-trunk/sqlalchemy/orm/query.py", line 620, in 
__iter__
    context = self._compile_context()
  File "/home/az/src/hor-trunk/sqlalchemy/orm/query.py", line 873, in 
_compile_context
    value.setup(context)
  File "/home/az/src/hor-trunk/sqlalchemy/orm/interfaces.py", line 
483, in setup
    self._get_context_strategy(querycontext).setup_query(querycontext, 
**kwargs)
  File "/home/az/src/hor-trunk/sqlalchemy/orm/strategies.py", line 
553, in setup_query
    value.setup(context, parentclauses=clauses, 
parentmapper=self.select_mapper)
  File "/home/az/src/hor-trunk/sqlalchemy/orm/interfaces.py", line 
483, in setup
    self._get_context_strategy(querycontext).setup_query(querycontext, 
**kwargs)
  File "/home/az/src/hor-trunk/sqlalchemy/orm/strategies.py", line 
553, in setup_query
    value.setup(context, parentclauses=clauses, 
parentmapper=self.select_mapper)
... last two repeated ...

more details tomorrow
ciao
svilen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to