Re: pgadmin4 setup.py, first time run

Yes, using flush does work.

regards,
Prasad Somwanshi
 
 

Sent: Tuesday, September 08, 2015 at 11:14 AM
From: "Ashesh Vashi" <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: "Ronan Dunklau" <ronan(dot)dunklau(at)dalibo(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, "Dave Page" <dpage(at)pgadmin(dot)org>, "Khushboo Vashi" <khushboo(dot)vashi(at)enterprisedb(dot)com>, Prasad <prasad(dot)s(at)mail(dot)com>
Subject: Re: [pgadmin-hackers] pgadmin4 setup.py, first time run

On Tue, Sep 8, 2015 at 2:54 PM, Ronan Dunklau <ronan(dot)dunklau(at)dalibo(dot)com> wrote:

If you want DML to be sent to the database with SQLAlchemy, you don't
necessarily need to commit: the flush() method will send all pending DML
operations without commiting.
What do you suggest - should we should use flush(...) instead of commit(...)?
 
Prasad,
 
As none of us is able to reproduce the issue at our end, can you please check flush instead of commit at your end?
 

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company[http://www.enterprisedb.com]
 
http://www.linkedin.com/in/asheshvashi[http://www.linkedin.com/in/asheshvashi]

Le Monday 07 September 2015 18:31:58 Ashesh Vashi a écrit :
> On Mon, Sep 7, 2015 at 6:29 PM, Dave Page <dpage(at)pgadmin(dot)org[dpage@pgadmin.org]> wrote:
> > On Mon, Sep 7, 2015 at 1:53 PM, Khushboo Vashi
> >
> > <khushboo(dot)vashi(at)enterprisedb(dot)com[khushboo(dot)vashi@enterprisedb.com]> wrote:
> > > On Mon, Sep 7, 2015 at 5:28 PM, Dave Page <dpage(at)pgadmin(dot)org[dpage@pgadmin.org]> wrote:
> > >> On Mon, Sep 7, 2015 at 12:36 PM, Khushboo Vashi
> > >>
> > >> <khushboo(dot)vashi(at)enterprisedb(dot)com[khushboo(dot)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[https://github.com/sasaporta/flask-security-admin-example/blob/master/main]
> > .py
> >
> > http://git.twopicode.com/nickw/flask-boilerplate/raw/f954ccd6e3269b043d0b3[http://git.twopicode.com/nickw/flask-boilerplate/raw/f954ccd6e3269b043d0b3]
> > 3b3be1c3bfb90c358d3/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.
> >
> > OK, well it won't hurt to have an extra commit in there. Ashesh; can
> > you commit this change please?
>
> Sure.
>
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company> <http://www.enterprisedb.com[http://www.enterprisedb.com]>
>
>
> *http://www.linkedin.com/in/asheshvashi*[http://www.linkedin.com/in/asheshvashi*]
> <http://www.linkedin.com/in/asheshvashi[http://www.linkedin.com/in/asheshvashi]>

>
> > --
> > Dave Page
> > Blog: http://pgsnake.blogspot.com[http://pgsnake.blogspot.com]
> > Twitter: @pgsnake
> >
> > EnterpriseDB UK: http://www.enterprisedb.com[http://www.enterprisedb.com]
> > The Enterprise PostgreSQL Company
 --
Ronan Dunklau
http://dalibo.com[http://dalibo.com] - http://dalibo.org[http://dalibo.org]