[web2py] Re: DAL caching values automatically?
This solved it (in models/db.py):
db.executesql('SET SESSION TRANSACTION ISOLATION LEVEL READ
COMMITTED;')
Muchas gracias, nick
On Nov 17, 12:09 pm, John Duddy wrote:
> I think you may have nailed it - my cron does run continuously.
>
> I always commit my transactions. Do you know how to force it to reset
> manually?
>
> On Nov 16, 9:17 pm, nick name wrote:
>
>
>
>
>
>
>
> > Does your cron program run continuously? what database are you using?
>
> > If you are using a database that supports mvcc (Oracle, Postgres, MySQL
> > with InnoDB tables, possibly others), your first select (of any kind, not
> > just this query) logically freezes the state of the database, and you will
> > not see any updates until you start a new transaction (which would happen
> > by starting the cron job again, but might be done manually).
>
> > Lookup ACID trait of databases - you might be seeing the I=Isolated
> > property in action.
[web2py] Re: DAL caching values automatically?
I think you may have nailed it - my cron does run continuously. I always commit my transactions. Do you know how to force it to reset manually? On Nov 16, 9:17 pm, nick name wrote: > Does your cron program run continuously? what database are you using? > > If you are using a database that supports mvcc (Oracle, Postgres, MySQL > with InnoDB tables, possibly others), your first select (of any kind, not > just this query) logically freezes the state of the database, and you will > not see any updates until you start a new transaction (which would happen > by starting the cron job again, but might be done manually). > > Lookup ACID trait of databases - you might be seeing the I=Isolated > property in action.
[web2py] Re: DAL caching values automatically?
Does your cron program run continuously? what database are you using? If you are using a database that supports mvcc (Oracle, Postgres, MySQL with InnoDB tables, possibly others), your first select (of any kind, not just this query) logically freezes the state of the database, and you will not see any updates until you start a new transaction (which would happen by starting the cron job again, but might be done manually). Lookup ACID trait of databases - you might be seeing the I=Isolated property in action.
