Using python 2.6.5 and facebook-sdk 0.3.2 this:
import facebook
api = facebook.GraphAPI(token)
api.fql({'example':u"SELECT uid2 FROM friend WHERE uid1 = me()"})
returns an empty list, but this
api.fql({'example':"SELECT uid2 FROM friend WHERE uid1 = me()"})
works. If any of the queries are unicode strings, the result will be [] with no error.
Facebook developer support suggested I ask on stackoverflow what's wrong. Their explanation was that since nobody else has reported this bug, that it's probably something I'm doing wrong. So they closed the bug.
Thoughts on how to deal with this?
It's based on how the facebook.py libraries handles the queries. Queries to Facebook all end up needing to be URL encoded.
So, digging through the facebook.py source
api.fql({'example':"SELECT uid2 FROM friend WHERE uid1 = me()"})
ends up as
queries%3D%7B%27example%27%3A+%27SELECT+uid2+FROM+friend+WHERE+uid1+%3D+me%28%29%27%7D
Which matches properly as
queries={'example': 'SELECT uid2 FROM friend WHERE uid1 = me()'}
where as
api.fql({'example':u"SELECT uid2 FROM friend WHERE uid1 = me()"})
ends up as
queries%3D%7B%27example%27%3A+u%27SELECT+uid2+FROM+friend+WHERE+uid1+%3D+me%28%29%27%7D
Notice that no handling of u for the unicode part was done before sending to urlencode in the facebook.py library.
https://api.facebook.com, returns no response to this but if you did the same at the graph.facebook.com endpoint you will notice
(#601) Parser error: unexpected '{' at position 0."
Basically, it chokes on your query.
Try dealing with your Unicode before sending off for Url Encoding
Maybe the problem is that you are mixing and matching the ASCII string on the left parameter with 'example', and using unicode on the right for the query string. Try this:
api.fql({u'example':u"SELECT uid2 FROM friend WHERE uid1 = me()"})
Try it the other way like this:
api.fql({u'example':"SELECT uid2 FROM friend WHERE uid1 = me()"})
I've known to show respect for the wild wooly world of unicode, maybe you are not encoding your ascii string correctly? Maybe try assembling your unicode string character by character with the unichr(...) command.
If fiddling around with these doesn't fix the problem, then the conclusion is that the fql function pukes when passed unicode. The work around is to always use ASCII strings.
Source: http://docs.python.org/howto/unicode.html
