I just learned to read, sorry.You mean not to do the second thing, which i do want to do (where each frontend user equals a database user).Thank you for your advise.I´m not sure if i can get around it, but i´ll use extra caution anayway.
WBLOn 10/27/06, Willy-Bas Loos [EMAIL PROTECTED] wrote:
My
On Thu, Oct 26, 2006 at 12:27:49AM +0200, Willy-Bas Loos wrote:
or will not receive those, because of the rights granted to him. These
granted rights and roles will be determined by the regular postgres
functionality (and some views).
Ah, that's a different matter. My suggestion is don't do
Hi,I´m envolved in developping a website that will function as a frontend for psql 8.1 cluster.We use a number of frontend technologies, and we want to keep the authentication in the backend. Not a system where the frontend queries a table to verify username password, sets the priviliges on the
I think that´s not exactly what i´m looking for.Just to make sure that i understand what you´re proposing (please correct me if i´m wrong):I´ll write a function that will create a hash of username, password and, say 'now'::timestamp and store it in a cookie and in a separate table somewhere on the
