Re: pgadmin4 setup.py, first time run - Mailing list pgadmin-hackers

From Khushboo Vashi
Subject Re: pgadmin4 setup.py, first time run
Date
Msg-id CAFOhELc--=-K31AmSDaUJePyBmmOAXW_ZqgiUnEzLG+YbYZTOA@mail.gmail.com
Whole thread Raw
In response to Re: pgadmin4 setup.py, first time run  (Dave Page <dpage@pgadmin.org>)
Responses Re: pgadmin4 setup.py, first time run  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers


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. 

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.


Thanks,
Khushboo
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: pgadmin4 setup.py, first time run
Next
From: Khushboo Vashi
Date:
Subject: Re: pgadmin4 setup.py, first time run