Re: pgadmin4 setup.py, first time run
| От | Khushboo Vashi |
|---|---|
| Тема | Re: pgadmin4 setup.py, first time run |
| Дата | |
| Msg-id | CAFOhELc--=-K31AmSDaUJePyBmmOAXW_ZqgiUnEzLG+YbYZTOA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pgadmin4 setup.py, first time run (Dave Page <dpage@pgadmin.org>) |
| Ответы |
Re: pgadmin4 setup.py, first time run
|
| Список | 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.
I have followed below links for SQLAlchemyUserDatastore, so I thought this way.
https://github.com/sasaporta/flask-security-admin-example/blob/master/main.py
http://git.twopicode.com/nickw/flask-boilerplate/raw/f954ccd6e3269b043d0b33b3be1c3bfb90c358d3/WebApp/Application/__init__.py
https://github.com/sasaporta/flask-security-admin-example/blob/master/main.py
http://git.twopicode.com/nickw/flask-boilerplate/raw/f954ccd6e3269b043d0b33b3be1c3bfb90c358d3/WebApp/Application/__init__.py
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 по дате отправления: