Re: 7.4 Press Release -- Draft #4 - Mailing list pgsql-advocacy

From Robert Treat
Subject Re: 7.4 Press Release -- Draft #4
Date
Msg-id 1059423331.22259.818.camel@camel
Whole thread Raw
In response to Re: 7.4 Press Release -- Draft #4  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: 7.4 Press Release -- Draft #4
List pgsql-advocacy
On Sat, 2003-07-26 at 21:31, Gavin Sherry wrote:
> > >    - Read only transactions, bringing a greater level of security to web and
> > >      enterprise applications by protecting data from modification.
>
> This should be removed. Even though I added it to the press release, I've
> just realised it's not really a security measure against SQL injection
> since injected code can just specify 'SET TRANSACTION READ WRITE'. We
> should still mention it, but not as a security measure.
>

Aside from spec compliance, whats the bonus for having it then? Or put a
better way, why/when would I want to use this?

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


pgsql-advocacy by date:

Previous
From: Josh Berkus
Date:
Subject: 7.4 Press Release
Next
From: "Nick Fankhauser"
Date:
Subject: Re: 7.4 Press Release -- starting Draft #5