On 12/10/15 22:52, Steve Petrie, P.Eng. wrote:
[...]
BTW -- this PostgreSQL newbie (bye bye mysql) is getting a nice warm
fuzzy feeling, about PostgreSQL and its amazingly helpful community :)
[...]
I can attempt to remedy your 'nice warm fuzzy feeling'! :-)
More seriously:
(1) why did you
ne" <floripa...@gmail.com>
To: "Steve Petrie, P.Eng." <apet...@aspetrie.net>;
<pgsql-general@postgresql.org>
Sent: Sunday, October 11, 2015 11:58 PM
Subject: Re: [GENERAL] *** QUESTION *** After successful 'BEGIN;' command --
why PGSQL_TRANSACTION_ACTIVE and no
Monday, October 12, 2015 5:22 AM
Subject: Re: [GENERAL] *** QUESTION *** After successful 'BEGIN;' command --
why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
Steve Petrie, P.Eng. wrote:
And yes, I am using pg_send_query(...) to execute the BEGIN; command, so
as
to get a result
Steve Petrie, P.Eng. wrote:
> And yes, I am using pg_send_query(...) to execute the BEGIN; command, so as
> to get a result resource returned. (Please see my forthcoming emailed
> response to Adrian Klaver, wherein I provide the PHP source code that Adrian
> requests.)
After
> ETO::0::LOG: 0: connection received: host=127.0.0.1
> port=1083
> ETO::0::LOCATION: BackendInitialize,
> src\backend\postmaster\postmaster.c:3850
> ETO::0::LOG: 0: connection authorized: user=its-eto_pg36
> database=eto_sql_db
> ETO::0::LOCATION:
(Thanks to Adrian Klaver & Rob Stone, for their responses to my earlier
posting, subject "[GENERAL] BEGIN, END & ROLLBACK commands -- do they produce a
SQLSTATE value?". I worked around the unavailability of sqlstate '0' after
a successful SQL command, by creating proxy PHP variables
On 10/10/2015 11:43 AM, Steve Petrie, P.Eng. wrote:
(Thanks to Adrian Klaver & Rob Stone, for their responses to my earlier
posting, subject "[GENERAL] BEGIN, END & ROLLBACK commands -- do they
produce a SQLSTATE value?". I worked around the unavailability of
sqlstate '0' after a successful
