Re: [GENERAL] Securing a db app - RFC

2004-06-02 Thread Shridhar Daithankar
On Wednesday 02 June 2004 17:58, [EMAIL PROTECTED] wrote: > > You can probably use set session authorization. Here are some brief > > steps. > > > > 1. Convert all your users as postgresql database users > > If he's going to do this, why bother with hard-coding a single user id > and password in th

Re: [GENERAL] Securing a db app - RFC

2004-06-02 Thread btober
> On Wednesday 02 June 2004 02:04, BARTKO Zoltan wrote: >> I would appreciate anyone wiser than me to comment on the following: >> >> I am making an app for PostgreSQL (the server). The clients are >> connecting through the same single user. ... >> >> If I want to access a function (like do this o

Re: [GENERAL] Securing a db app - RFC

2004-06-02 Thread Shridhar Daithankar
On Wednesday 02 June 2004 02:04, BARTKO Zoltan wrote: > I would appreciate anyone wiser than me to comment on the following: > > I am making an app for PostgreSQL (the server). The clients are connecting > through the same single user. There is a model of the user organization > inside (position hi

[GENERAL] Securing a db app - RFC

2004-06-01 Thread BARTKO Zoltan
Hello folks,   First a question and then the rest:   Does the PostgreSQL log contain the stored function calls with all parameters? Or is this something that could be set?   I would appreciate anyone wiser than me to comment on the following:   I am making an app for PostgreSQL (the server). T