Open GoogleCodeExporter opened 9 years ago
hint:
my home server:
everything OK, php 5.3.6, sqlite 3.7.4
production server:
this ugly bug, php 5.3.8, sqlite 3.3.6
Original comment by stra...@seznam.cz
on 3 Nov 2011 at 9:30
seems a write permission issue..
1. all "db" folders (application/db, and modules/{module}/db) need to be 777
(recursive).
2. after a bit of google search.. i've found:
http://www.sqlitemanager.org/en/tips/php-sqlite3/database-table-is-locked.html
I never used "closeCursor()" method, but we can try to add this after each
"fetchAll" or "fetch" ... or just in the "execute" method of this driver:
http://code.google.com/p/rapyd-framework/source/browse/trunk/core/libraries/driv
ers/database_pdo.php
can you try to play with this?
Original comment by felice.ostuni
on 4 Nov 2011 at 8:40
I tried second option. I added one row in execute function in database_pdo.php
file and now it seems to be OK. Thanks a lot for help.
My modified function now looks that:
protected function execute($sql)
{
//rrr : reset result resources
if (is_object ($this->result_id)){ $this->result_id->closeCursor(); }
$this->pdo_results = '';
$this->pdo_index = 0;
$this->result_id = FALSE;
$this->result_array = array();
$this->result_object = array();
return $this->conn_id->query($sql);
}
If I detect some bad side effect, I will post it here.
Original comment by stra...@seznam.cz
on 4 Nov 2011 at 10:44
perfect, I'll try this patch on some other env. then I'll commit.
thnks for reporting.
Original comment by felice.ostuni
on 7 Nov 2011 at 11:24
Original issue reported on code.google.com by
stra...@seznam.cz
on 3 Nov 2011 at 9:01