[firebird-support] php transactions

2016-07-12 Thread 'Daniel Miller' dmil...@amfes.com [firebird-support]
I have an application I'm developing with PHP & Firebird.  While it 
mostly works fine - I've been having what I believe to be transaction 
issues.


One problem was visibility - committed changes were not visible to 
selects.  I know they were committed - after executing the commit within 
the scripts, I could see the changes within FlameRobin.  Yet the script 
didn't see them.


I also saw the "oldest active transaction" getting old...and it didn't 
seem to update until I killed some of the longer-running php processes.


I use explicit transactions for every insert or update followed by 
explicit commits.  Could my problem be that I need to use explicit 
transactions for the selects as well?


--
Daniel

Re: [firebird-support] php transactions

2016-07-12 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
12.07.2016 22:28, 'Daniel Miller' dmil...@amfes.com [firebird-support] wrote:
> Could my problem be that I need to use explicit transactions for the selects 
> as well?

   Yes.


-- 
   WBR, SD.






++

Visit http://www.firebirdsql.org and click the Documentation item
on the main (top) menu.  Try FAQ and other links from the left-side menu there.

Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ 

++


Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/firebird-support/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/firebird-support/join
(Yahoo! ID required)

<*> To change settings via email:
firebird-support-dig...@yahoogroups.com 
firebird-support-fullfeatu...@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
firebird-support-unsubscr...@yahoogroups.com

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/



Re: [firebird-support] php transactions

2016-07-13 Thread Lester Caine les...@lsces.co.uk [firebird-support]
On 12/07/16 21:28, 'Daniel Miller' dmil...@amfes.com [firebird-support]
wrote:
> I have an application I'm developing with PHP & Firebird.  While it
> mostly works fine - I've been having what I believe to be transaction
> issues.

Nice to see a new PHP user Daniel we do have a list for firebird-php
http://groups.yahoo.com/group/firebird-php/http://groups.yahoo.com/group/firebird-php/

The default settings for a firebird connection are not ideal, I use
adodb for all my database interfacing and that sets the default to
$this->ibasetrans = IBASE_WAIT | IBASE_REC_VERSION | IBASE_COMMITTED;
http://adodb.org is worth a look if you are doing anything heavy or
cross database.

Re using commit or rollback - any uncommitted stuff simply gets rolled back.

-- 
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk


Re: [firebird-support] php transactions

2016-07-13 Thread Tim Ward t...@telensa.com [firebird-support]
On 12/07/2016 21:28, 'Daniel Miller' dmil...@amfes.com 
[firebird-support] wrote:


I have an application I'm developing with PHP & Firebird.  While it 
mostly works fine - I've been having what I believe to be transaction 
issues.
One problem was visibility - committed changes were not visible to 
selects.  I know they were committed - after executing the commit 
within the scripts, I could see the changes within FlameRobin.  Yet 
the script didn't see them.
I also saw the "oldest active transaction" getting old...and it didn't 
seem to update until I killed some of the longer-running php processes.
I use explicit transactions for every insert or update followed by 
explicit commits.  Could my problem be that I need to use explicit 
transactions for the selects as well?




Quite likely. If you have a long running PHP process which does lots of 
selects and never does a commit it'll quite likely all be in one 
transaction which can produce the symptoms you describe.


--
Tim Ward