Re: updateable cursors & visibility

Hiroshi Inoue,

But still can't explain this:
SENSITIVE => not READ_ONLY
It's in the ODBC Spec.
>Bruce Momjian wrote:
>>
>> Sorry, no idea. Peter's idea is that FOR UPDATE requires SENSITIVE, so
>> INSENSITIVE has to be READONLY because the update has to see other
>> changes to be accurate.
>>
>> I think clearly SENSITIVE/READONLY should be possible, so:
>>
>> READONLY/SENSITIVE possible
>> READONLY/INSENSITIVE possible
>> FOR UPDATE/SENSITIVE possible
>> FOR UPDATE/INSENSITIVE not possible
>>
>> READONLY can be either way, while FOR UPDATE requires SENSITIVE.
>
>SENSITIVE doesn't mean *not INSENESITIVE*.
>INSENSITIVE doesn't mean *not SENSITIVE*.
>
>regards,
>Hiroshi Inoue
> http://www.geocities.jp/inocchichichi/psqlodbc/
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

Regards!

　　　　　　　　Han
　　　　　　　　zhouhanok(at)vip(dot)sina(dot)com
　　　　　　　　　　2003-03-28