I assume you're using the standard PDO driver? I don't have PostgreSQL handy at the moment, but I can test with MariaDB, the result should be the same due to the PDO abstraction.
Can you check if you have the above changes locally? Because that commit fixes exactly this issue (no data being returned).
We run all our production apps on 1.9/develop, so for the moment I think that if there was a serious framework error, we would have noticed it by now?
I've got the latest commit locally. I try to check the operation on MariaDB / MySQL using the PDO and everything works correctly! So there is only problem with PostgreSQL.
Please analyze the following queries and responses:
I don't understand why this can happen, PDO is PDO, there is no RDBMS specific code in the PDO driver, and PDO does the abstaction, all the driver does is do a PDO Fetch, which is the same for both PostgreSQL and MySQL?
I think I found a problem. In the above tests for Postgres I had the directive enable_cache=false; for MySQL I didn't have it at all (default is enable_cache=true). I noticed this checking for you what the execute () method returns :)
For Postgres it was Fuel\Core\Database_PDO_Result object, and for MySQL Fuel\Core\Database_PDO_Cached. Try to switch enable_cache to false to check what happend in your projects.
Hmm... That should still work, that was wat that last commit was about. Does that mean your MySQL test will also fail when you disable the cache?
When you process the result. with cache false, one record is fetched from the result for every request to the result, with cache true, all records in the result are fetched immediately, and you iterate over the stored result.
No cache takes less memory compared to cache (especially when the result sets are large), but with the case you have direct access, so you can see, fetch previous and next, restart at the beginning, etc.