I've posted a question on Stack Overflow that I suspect is actually a bug in either HDBC or HDBC-sqlite3.
So, I deeply apologize for the cross posting of this problem, and hope you'll be able to forgive me.
The problem is related to an integer argument to a longer query. When the integer is passed as an argument to the query, the result is an empty set. When the integer is hard coded in the actual query instead, the result is what is expected. Please have a look if there could be an issue in handling of SqlInt64 in parameters. I am on OSX 10.10.
Hi,
I've posted a question on Stack Overflow that I suspect is actually a bug in either HDBC or HDBC-sqlite3. So, I deeply apologize for the cross posting of this problem, and hope you'll be able to forgive me.
http://stackoverflow.com/questions/29040880/generating-long-sqlite3-queries-in-haskell-hdbc
The problem is related to an integer argument to a longer query. When the integer is passed as an argument to the query, the result is an empty set. When the integer is hard coded in the actual query instead, the result is what is expected. Please have a look if there could be an issue in handling of SqlInt64 in parameters. I am on OSX 10.10.
Fredrik