Heikki, > FOR READ ONLY is actually part of the SELECT syntax. It's been accepted > for at least down to version 7.4, probably even longer than that, but it > hasn't been documented. It's accepted for the sake of compatibility with > other DBMSs (and SQL standard?), it doesn't do anything in PostgreSQL. > > Now, whether we should make an effort to not allow updating a cursor on > a query with FOR READ ONLY, that's another question. I don't think it's > worth the effort, and it wouldn't really gain us anything. We probably > should mention it in the manual, in the Compatibility section of SELECT > reference page.
Who are we, MySQL? We ought not to accept the syntax if we're not going to enforce it. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
