"READ-COMMITTED" isolation level only see data committed. Closing (commit or revert) transaction is required for other transaction can see new data anyway.
On Tue, Jun 2, 2015 at 3:28 PM, Manivel Rajendran <[email protected]> wrote: > My MYSQL's transaction isolation level is "READ-COMMITTED" > > On Tue, Jun 2, 2015 at 11:38 AM, INADA Naoki <[email protected]> > wrote: > >> How do you use MySQL? >> >> MySQL's default transaction isolation level is "repeatable read". >> If you didn't close transaction properly for each requests, you'll see >> data for time you start transaction. >> >> On Tue, Jun 2, 2015 at 2:40 PM Manivel Rajendran <[email protected]> >> wrote: >> >>> Hi, >>> >>> I am using MySQL as my backend for my django website and I have >>> configured it with nginx via uwsgi. Everything is working fine. But some >>> times when I update any record and it is updated in mysql, at the same time >>> it shows the old data in another page, which lists all the records. When I >>> reload the uwsgi, then the page shows the latest updated data.I am not >>> facing any of this problem, when I run the project directly. >>> >>> >>> >>> *Best RegardsManivel Rajendran* >>> >>> _______________________________________________ >>> uWSGI mailing list >>> [email protected] >>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >>> >> >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> >> > > > > > *Best RegardsManivel Rajendran* > > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > -- INADA Naoki <[email protected]>
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
