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<set transaction read only>" 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. This third value could mean "Make it read-only, if you can, > otherwise throw an exception".
I can see some value in it, I'm just not sure it's worth it. There's the question of picking 'magic value' to represent it. There's also the issue of how different databases and drivers may differ in the degree to which they can support it. We can return to it later. For now I'm happy to just document it as a boolean and that only 0 and 1 should be used. Tim.