Hi,
I came across this mail from Fred Giasson in the SF list archive [1]:
Hi Everybody,
I am facing long read issue with one of my server (when sparqling). The
server runs:
(1) Virtuoso 5.12.3041
(2) PHP 5.3.2
(3) It uses the default unixodbc drivers that comes with ubuntu
(4) I am using
On 4/16/12 1:38 PM, Will Daniels wrote:
OK forget this, it's definitely a PHP problem.
Sorry for the noise.
-Will
Yes, but we get the blame for everything :-)
Now I have to ponder about what's making Debian feel it makes sense to
move away from iODBC .
Kingsley
On 16/04/12 12:37,
HI Will,
OK forget this, it's definitely a PHP problem.
Sorry for the noise.
If you can tell me what is going wrong with PHP, i still maybe able to help by
sending them a bugfix if need be.
Patrick
---
Maintainer iODBC
Hi Patrick,
On 16/04/12 20:15, Patrick van Kleef wrote:
If you can tell me what is going wrong with PHP, i still maybe able to help by
sending them a bugfix if need be.
I think it has to do with allocation of the default read buffer in PHP ODBC
module somehow. After checking that it worked
On 16/04/12 18:42, Kingsley Idehen wrote:
Now I have to ponder about what's making Debian feel it makes sense to move away
from iODBC .
I read it in a Launchpad bug[1], comment from Steve Langasek (vorlon):
The oneiric tdsodbc Recommends: libiodbc2 | unixodbc, so libiodbc2 gets pulled
in
Hi Everybody,
I am facing long read issue with one of my server (when sparqling). The
server runs:
(1) Virtuoso 5.12.3041
(2) PHP 5.3.2
(3) It uses the default unixodbc drivers that comes with ubuntu
(4) I am using DB.DBA.SPARQL_EVAL to wrap the sparql queries via the
PHP-ODBC API.
So,
