On 5/4/07, Scott Smith <[EMAIL PROTECTED]> wrote:
I don't know if/how other databases implement this feature, and give it
such a possibly misleading name. Does anyone else?
I wouldn't consider it misleading.
This is the way SET TRANSACTION works in Oracle, regardless of whether
or not it i
On Wed, May 09, 2007 at 02:33:23PM -0400, Steven Lembark wrote:
>
> > Any thoughts?
>
> Amen: Most of the perl I use only does reads and
> the readonly locking could be a big savings.
I trust you'll be sending patches to the authors of the drivers you're
using... :)
Tim.
> Any thoughts?
Amen: Most of the perl I use only does reads and
the readonly locking could be a big savings.
--
Steven Lembark 85-09 90th Street
Workhorse Computing Woodhaven, NY 11421
[EMAIL PROTECTED]
Tim Bunce wrote:
On Fri, May 04, 2007 at 08:15:53AM -0500, Scott Smith wrote:
Doing "set transaction read only" on Oracle has additional side-effects
besides making the connection unable to write: it switches the read
consistency level from per-statement (the default) to per-transaction.
Th
On Fri, May 04, 2007 at 08:15:53AM -0500, Scott Smith wrote:
> Doing "set transaction read only" on Oracle has additional side-effects
> besides making the connection unable to write: it switches the read
> consistency level from per-statement (the default) to per-transaction.
>
> This effective
Doing "set transaction read only" on Oracle has additional side-effects
besides making the connection unable to write: it switches the read
consistency level from per-statement (the default) to per-transaction.
This effectively freezing the connection in time, allowing multiple
queries to be e
Ooops; most of the mailing lists I work with redirect responses to the
list. I forget this one doesn't.
-- Forwarded message --
From: Jonathan Leffler <[EMAIL PROTECTED]>
Date: May 1, 2007 6:32 AM
Subject: Re: Proposal for new $h->{ReadOnly} attribute
To: &
On Tue, May 01, 2007 at 10:43:40AM +0200, H.Merijn Brand wrote:
> On Mon, 30 Apr 2007 14:56:37 +0100, Tim Bunce <[EMAIL PROTECTED]> wrote:
>
> > I've just added this to the DBI docs:
> >
> > =item C (boolean, inherited)
> >
> > An application can set the C attribute of a handle to a true
> > va
On Mon, 30 Apr 2007 14:56:37 +0100, Tim Bunce <[EMAIL PROTECTED]> wrote:
> I've just added this to the DBI docs:
>
> =item C (boolean, inherited)
>
> An application can set the C attribute of a handle to a true value
> to
> indicate that it will not be attempting to make any changes (insert, de
On Mon, Apr 30, 2007 at 04:39:05PM +0200, Jochen Wiedmann wrote:
> On 4/30/07, Tim Bunce <[EMAIL PROTECTED]> wrote:
>
> >If the driver can make the handle truely read-only (by issing a statement
> >like
> >"C" as needed, for example) then it should.
> >Otherwise the attribute is simply advisory.
On Apr 30, 2007, at 6:56 AM, Tim Bunce wrote:
I've just added this to the DBI docs:
=item C (boolean, inherited)
I like it!
Another use case is in typical replicated setups with some write
nodes and some read-only nodes.
- ask
--
http://develooper.com/ - http://askask.com/
On 4/30/07, Tim Bunce <[EMAIL PROTECTED]> wrote:
If the driver can make the handle truely read-only (by issing a statement like
"C" as needed, for example) then it should.
Otherwise the attribute is simply advisory.
For reading the value, I agree. I'd like to see a third value when
writing. Th
I've just added this to the DBI docs:
=item C (boolean, inherited)
An application can set the C attribute of a handle to a true value to
indicate that it will not be attempting to make any changes (insert, delete,
update etc) using that handle or any children of it.
If the driver can make the ha
13 matches
Mail list logo
