this is definitely not related to any issue from 2007.   See what happens if 
you call sqlalchemy.orm.configure_mappers() right before you emit that Query in 
this particular test.    the error indicates this particular class was not 
present when the mappers post-configured themselves.


On Oct 4, 2013, at 4:10 AM, kim <k...@hyunjun.kr> wrote:

> T_T
> 
> Hi, I am using SQLAlchemy 0.8.2 with PostgreSQL and having exactly same 
> problem.
> 
> I have a lot of table classes inherited declarative base and only some of 
> classes raise errors. (https://gist.github.com/yoloseem/d1c9b0f8d3cef6c196e4)
> 
> Actually, even for same buggy classes, errors are appeared in some special 
> environment (for me, calling exactly same function works well in web 
> view(Flask) or shell context but always erroneous in Celery task).
> 
> To figure out what causes this, I've turn logging level for 'sqlalchemy.orm' 
> to INFO,
> and I found some differences between tables working well and error causing 
> tables. (https://gist.github.com/yoloseem/b20cb4a283212ceb0439)
> Working things printed out about "_post_configure_properties()" and buggy 
> things printed out about "Identified primary key columns".
> 
> please somebody help me? !!
> 
> 
> 2007년 11월 24일 토요일 오전 4시 6분 3초 UTC+9, Michael Bayer 님의 말:
> 
> On Nov 23, 2007, at 12:53 PM, lur ibargutxi wrote:
> > my problem is that in my local configuration I have SQLAlchemy0.4.0  
> > and collective.lead and my aplication work very well but when i try  
> > to do the same thing in the server I have this problem:
> >
> > ArgumentError: Error determining primary and/or secondary join for  
> > relationship ' Areas.idareatype2 (Areatypes)'. If the underlying  
> > error cannot be corrected, you should specify the 'primaryjoin' (and  
> > 'secondaryjoin', if there is an association table present) keyword  
> > arguments to the relation() function (or for backrefs, by specifying  
> > the backref using the backref() function with keyword arguments) to  
> > explicitly specify the join conditions. Nested error is "Can't find  
> > any foreign key relationships between 'areas' and 'areatypes'"
> >
> 
> ok....using table reflection for your tables (i.e. autoload=True)?   
> MySQL with MyISAM (the default) tables ?  foreign keys won't reflect  
> in that case, you have to either specify those columns in your Table  
> defs manually or use InnoDB tables in your MySQL database.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sqlalchemy" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sqlalchemy+unsubscr...@googlegroups.com.
> To post to this group, send email to sqlalchemy@googlegroups.com.
> Visit this group at http://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/groups/opt_out.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to