On Tuesday, January 14, 2014 9:56:25 AM UTC-5, Richard wrote:
Notice migrate_neabled=False as notting to do with read only, it only tell
to web2py to not migrate apply to the models in models.py. It is more of a
complement.
The point is that if two applications are accessing the database,
Notice migrate_neabled=False as notting to do with read only, it only tell
to web2py to not migrate apply to the models in models.py. It is more of a
complement.
You may also consider to use auth permissions and set them to read and
select for every objects in your database for more sercure read
I have two web2py apps, one updates database the other app should just
read. But i want the readonly app to have its own db to ready from with
selected tables from the main db. Whats the best way to replicate selected
tables and monitor changes to main db. Secondly what would be the
configuration
web2py readonly :
You implement select only in your app function everywhere :
db().select()
SQLFORM(..., readonly=True)
SQLFORM.grid(..., deletable=False, editable=False, create=Flase,
details=True, selectable=True)
Replication :
An audit trail on your table that received the new data should
Also, set DAL(..., migrate_enabled=False) to prevent migrations.
Anthony
On Monday, January 13, 2014 2:35:40 PM UTC-5, Richard wrote:
web2py readonly :
You implement select only in your app function everywhere :
db().select()
SQLFORM(..., readonly=True)
SQLFORM.grid(...,
Brilliant, am using mural db...have found an inbuilt replication feature in
mysql. So will try out the dam(..., migrate_enabled=False) feature for read
only. And of course will use only select statements in the read only app.
Thanx
On 13 Jan 2014 21:42, Anthony abasta...@gmail.com wrote:
Also,
6 matches
Mail list logo
