Search Postgresql Archives
Re: acessibility for tables
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Do you mean, you want everyone to see the data, but only the "owner" can
Also, you asked if this is a good idea.
I would like to modify not only one field, but rather the whole record.
No problem, only don't let them change the owner
I thin NEW is the record of the view with the updated data and OLD the
orginal records (similar to trigger & stored procedure).
I would like to set OLD to NEW if the owner field is correct like:
No need to do that. The UPDATE does this already. If you change NEW, then you are changing what the UPDATE does.
Can I do this with the rule on the view?
You could, but you should definitely look into triggers, like Albe said.
Well, it works. But it is certainly not advisable to use the postgres authorisation system for anything else than postgres. I mean, don't try to use this for a web site of sorts.
Then there are other ways to do it, if you really just want to make a database. Maybe inheritance could come in handy: a table per user and a parent table with select-only rights for all. (http://www.postgresql.org/docs/9.1/static/ddl-inherit.html)
"Quality comes from focus and clarity of purpose" -- Mark Shuttleworth
[PHP on Windows]
[Find Someone Nice]
[Postgresql & PHP]