On Mon, Sep 7, 2015 at 5:28 PM, Dave Page <dpage@pgadmin.org> wrote:
On Mon, Sep 7, 2015 at 12:36 PM, Khushboo Vashi <khushboo.vashi@enterprisedb.com> wrote: > Hi Dave, > > I have tried to reproduce the issue but couldn't reproduce it on UBUNTU as > well as on MAC.
OK. > I have checked the online examples of SQLAlchemyUserDatastore, and I think > it is logical that before assigning the new role to the newly created user, > user should be committed first.
Any particular reason why? Queries within a given transaction should normally see changes made by other queries in the same transaction.
I have followed below links for SQLAlchemyUserDatastore, so I thought this way.
Also, I have read that, if the Role has already been created then we can assign that role while creating the new user. So, I thought Role should be committed first and then we can use it. May be this was my misunderstanding.