I think you have misunderstood... autocommit works as it always has in
7.4, the difference is that the logic to turn it off is now left to the
client side instead of trying to manage it within the server.
ie.
phppgadmin=# select version();
version
-------------------------------------------------------------
PostgreSQL 7.4 on i586-pc-linux-gnu, compiled by GCC 2.95.3
(1 row)
phppgadmin=# set autocommit = off;
ERROR: SET AUTOCOMMIT TO OFF is no longer supported
phppgadmin=#
Of course PostgreSQL is open source, so I always recommend for folks to
do a test installation and test there apps out just to be on the safe
side.
Robert Treat
On Sun, 2003-12-07 at 03:54, Sai Hertz And Control Systems wrote:
> Dear all ,
>
> Permit me to gain some of your most valuable knowledge ...........
>
> Our intrAnet server has the following spec
> 1. RH 9.0
> 2. Postgresql 7.3.4
> 3. PHP 4.3.3
> 4. GCC 3.2.2
>
> Till date my front end language (PHP) use to simply pass the data to
> postgresql in case of insert and
> update we were not using
> 1 BEGIN COMMIT block in PHP till date thanks to auto-commit-ON in postgreql
> 2. ROLLBACK script in PHP script
>
>
> And now when our company has decided to switch over to postgresql 7.4
> we have some doubt
> 1. Do we have to include BEGIN and COMMIT block around the insert
> process . (Because Postgresql 7.4 has auto-commit-OFF) in our PHP scripts
> 2. Not only this do we also have to port the pgSQL functions which use
> to do inserts into a third table such that
> data gets committed on function execution
>
>
> Please provide us any kinda information so that we can happily switch to
> postgressql 7.4
>
>
>
> Regards,
> V Kashyap
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
