| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
| Cc: | Prasad <prasad(dot)s(at)mail(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgadmin4 setup.py, first time run |
| Date: | 2015-09-07 11:58:19 |
| Message-ID: | CA+OCxozWTV6GRC02wZLy6YZD13Dp_AN4xUe7AMEUUjf82c=MkA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Mon, Sep 7, 2015 at 12:36 PM, Khushboo Vashi
<khushboo(dot)vashi(at)enterprisedb(dot)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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Khushboo Vashi | 2015-09-07 12:53:33 | Re: pgadmin4 setup.py, first time run |
| Previous Message | Prasad | 2015-09-07 11:57:35 | Re: pgadmin4 setup.py, first time run |