AW: The lightbulb just went on...

Zeugswetter Andreas SB <zeugswettera@wien.spardat.at>

From: Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>
To: "'Michael J Schout'" <mschout@gkg.net>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Date: 2000-10-19T08:21:04Z
Lists: pgsql-hackers
> what happens to sessions is that it does:
> 
> SELECT session_data, id 
> FROM   sessions
> WHERE  id = ?
> FOR UPDATE
> 
> .... client does some processing ...
> 
> UPDATE sesssions set session_data = ? WHERE id = ?;
> 
> (this is where the error happens)
> 
> I think part of my problem might be that sessions is a view 
> and not a table,

Did you create an on update do instead rule ?

This is currently not done automatically for views,
thus views without additional "create rule"s are select only.

But, I am wondering whether the "for update" places the correct lock ?

Andreas