On Fri, Jan 19, 2007 at 18:24:32 +0200,
Andrus <kobruleht2@hot.ee> wrote:
> > It might make more sense to use your own table of users and hashed
> > passwords
> > rather than postgres'. This would depend somewhat on the overlap of users
> > who
> > are using your application and those who connect directly to the database.
> > If there isn't much overlap, having a separate table is probably better.
>
> Using own table requires storing Postgres user name and password in client
> computer. Thus this information is available to virtually everyone haveing
> access to client computer.
> So this is very bad idea and should avoided at all.
No, the tables would be on the server, the same as was already being done.
Using a separate table makes it more future proof.
