On Wed, 26 Jan 2005, Fabio Tranchitella wrote:
I suspect this is the problem. For some reasons, this will result in two different updates to that table: one for the role, and one for the password. If you define that table to require (NOT NULL) both the fields, you'll never be able to write that table with exUserFolder, that's it.
This sounds reasonable because if two tables are expected you can not fullfil the request to have a NULL value first. So I guess the advanced mode is not what I really want for my application.
Maybe exUserFolder asks for two _different_ tables to store password and roles. I'll have a look on this today at lunch time, I hope.
However this works I do not really need this "advanced" method, if ...
Anyway, in the (simple) "Postgresql Authentication Source" the roles property seems not to be used. The roles I have set in the table are not displayed in the selection box if I want to change a user and if I for instance change a password of a user, the role is just set to NULL (which can be verified) in the database. Moreover I'm not able to login with the newly created passwords.
So something is *really* wrong here. Please tell me, which further information is needed.
Mmm, this sounds strange.. I'll check what happens in this scenario.
... this would work instead ...
Kind regards
Andreas.
-- http://fam-tille.de
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
