> > I can speculate that it works on other machines either because they do not > > have decoding_filter enabled or use different DB API driver. > > That's the same "everything" :-) This is a checkout from my own repository, > so all configurations are the same, so this is not in my code or > configuration files. > > It might be something related to my PostgreSQL drivers, though... Both > machines where it works (SuSE 9.3 and 10.0) have PostgreSQL 8.1.2 and the > machine where it doesn't work (SuSE 9.3 as well) has PostgreSQL 8.1.1... > Also, I use psycopg2 where it works and psycopg 1.1.6 where it doesn't, so > your assumption makes sense.
That's the key. IIRC, psycopg2 supports unicode queries while v1 does not. > But, I'll really upgrade my tools so that the ones on this server matches the > ones on the other two servers. I need the same environment for testing > purposes... :-) > > Thanks, Max! I believe this will help a lot of people, though. Maybe it is a > definite ending to questions like these (I hope!). :-) It's been bothering > us for a while now. I doubt this is a definite answer. The definite answer would be to fix SQLObject. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
