I've got no idea about the source of the problem, but it would probably be helpful if you could provide stack traces from the exceptions, if that's possible.
Other than that, I would have thought you should be able to track down the source of the 'global name' exception by grepping your source code for uses of 'anxnews_urllocal' without a '.' in front of it. Is it possible that you are doing something like this, for example: query.select_by(anxnews_urllocal > 5) When you probably mean: query.select_by(table.c.anxnews_urllocal > 5) Note that this is purely a Python exception - I can't think of any way SQLAlchemy can try and use one of your column names as a global variable. Hope that helps, Simon > -----Original Message----- > From: sqlalchemy@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of Roger Demetrescu > Sent: 11 April 2007 06:57 > To: sqlalchemy@googlegroups.com > Subject: [sqlalchemy] Re: 'PropertyLoader' object has no > attribute 'strategy' > > > Some details I forgot to mention: > > I'm using: > > * SQLAlchemy 0.3.6 > * Postgresql 7.3.4 > * Linux RedHat kernel 2.4.20-8 > > > Other important detail: looking at my log files, I noticed > that the message: > global name 'anxnews_urllocal' is not defined > > appears several hours after the message: > 'PropertyLoader' object has no attribute 'strategy' > > > Thanks > > Roger > > > On 4/11/07, Roger Demetrescu <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I have a daemon with 2 threads to control upload / download of some > > files (they use SQLAlchemy to find out which files must be worked). > > > > Once a week, my daemon's logging system sends me an email > with this message: > > > > 'PropertyLoader' object has no attribute 'strategy' > > > > > > > > After that, I receive another email with this message: > > > > global name 'anxnews_urllocal' is not defined > > > > where 'anxnews_urllocal' is a field from a table. > > > > > > > > I usually don't need to touch this daemon... it still works > fine even > > after this alert. > > > > Any hints about what could be causing this exception ? > > > > Please feel free to ask for more details... > > > > > > TIA > > > > Roger > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
