From: | Steven Klassen <sklassen(at)commandprompt(dot)com> |
---|---|
To: | Dennis Gearon <gearond(at)fireserve(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: connection or query affected |
Date: | 2004-10-12 16:24:31 |
Message-ID: | 20041012162431.GA1554@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Dennis Gearon <gearond(at)fireserve(dot)net> [2004-10-12 08:13:07 -0700]:
> turn off autocommit
Per connection.
> start transaction
> commit transaction
They're statements themselves that change the state of the
connection. You start a transaction, run your queries, and then
commit/rollback.
> SET schema
It depends if you're setting your search path for subsequent queries
which would be tracked per connection or you're actually prepending
the schema where the table exists in the query.
E.g.
$dbh->query("SET search_path='my_schema'");
- or -
$dbh->query('SELECT foo FROM my_schema.bar WHERE active');
--
Steven Klassen - Lead Programmer
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Replication & Support Services, (503) 667-4564
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2004-10-12 16:32:28 | Re: Message-ID as unique key? |
Previous Message | Eric D Nielsen | 2004-10-12 16:20:46 | Re: Need some advice on appropriate PL strategy... ["solved/thanks"] |