| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-advocacy(at)postgresql(dot)org, greg(at)turnstep(dot)com, Justin Clift <justin(at)postgresql(dot)org> |
| Subject: | Re: 7.4 Press Release |
| Date: | 2003-07-16 14:01:33 |
| Message-ID: | Pine.LNX.4.21.0307162359460.7844-100000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Tue, 15 Jul 2003, Joe Conway wrote:
> Robert Treat wrote:
> > uh, a little too technical for this release ;-)
>
> Yeah, I knew that. I just wanted to give you the details so you would
> understand what was behind my bullets.
>
> > - Read only transactions, which bring a greater level of
> > security to web and enterprise applications by protecting data
> > from modification.
>
> Hmmm, somehow I missed this change. How is it used?
START TRANSACTION ... READ ONLY
SET TRANSACTION ... READ ONLY
I missed it too. I pulled the reference out of HISTORY and padded. Its a
very useful feature on other database systems, particularly when READ
UNCOMMITTED is also implemented.
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2003-07-16 15:19:20 | warm and fuzzy |
| Previous Message | Robert Treat | 2003-07-16 12:09:02 | Re: 7.4 Press Release |