You can do:
DAL(...., migrate_enabled=False)
and no table will be migrated ever.
On Wednesday, 16 January 2013 23:41:42 UTC-6, Rick Ree wrote:
>
> Thanks Massimo.
>
> For this app we use migrate=False for all tables because of issues that
> arose in the context of distributed development using git. Basically,
> developers are using different MySQL servers, not all on localhost. So the
> *.table files were different, and so we did not put them in version
> control. With automatic migrations enabled, this seemed to cause problems
> when the database structure changed. Not sure if I am explaining this very
> clearly. In any case, we found it easier to manage table models manually,
> and distribute sql files for altering tables.
>
> I guess what this means is that using web2py's record versioning is not a
> good idea if we want to continue to avoid automatic migrations of the
> archive tables. If that is not the case, please enlighten me - thanks!
>
> -Rick
>
> On Wednesday, January 16, 2013 9:22:03 AM UTC-6, Massimo Di Pierro wrote:
>>
>> If you do
>>
>> db=DAL(...., migrate_enabled=True) # default behavior
>>
>> auth.enable_record_versioning(db)
>> db.define_table('something',...., migrate=False)
>> ...
>>
>> The migrate=False only affect the "something" table. If you change its
>> model that table will not migrate but associated archive table will.
>>
>> If instead migrate_enabled=False, none of the tables will migrate.
>>
>>
>>
>> On Tuesday, 15 January 2013 22:09:28 UTC-6, Rick Ree wrote:
>>>
>>> Hi,
>>>
>>> I would like to enable record versioning on an existing MySQL database
>>> in which all tables are managed manually (migrate=False). I am concerned
>>> about what happens if the structure of a table changes in db.define_table(
>>> ... ). Is the associated archive table changed to match accordingly?
>>>
>>> thanks,
>>> -Rick
>>>
>>
--
