| From: | Teunis Peters <teunis(at)wintersgift(dot)com> |
|---|---|
| To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Authentication blues |
| Date: | 2005-07-01 23:17:46 |
| Message-ID: | b823e52871fcc50bd2d067f165faa4b0@wintersgift.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I'm working on a PL/SQL set of functions to handle user access
restrictions to particular tables and am wondering:
- Is it "safe" to use postgresql authentication? Should I (like a LOT
of apps do) build my own authentication tables and just use a common
login/password for the application?
I'm honestly curious. My own suspicion is postgres authentication
(using postgres users/groups) is .. for the most part... safer.
also - are there any examples of per-record restrictions on a username
basis in pl/sql? I've been working on this a couple weeks and am
stuck - and can't find any examples on either postgresql or oracle.
(Oracle has the feature built-in from what I can tell...)
Ta!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Schmidt | 2005-07-02 01:09:36 | Re: Check Constraint problem |
| Previous Message | Thomas F. O'Connell | 2005-07-01 20:45:40 | PostgreSQL Hosting |