Hi Senthil, Antonio
I know the cause. The migration script should be re-generated not just
rename.
Thanks for the fixing. :)
Arthur
2013/11/13 Senthil Kumaran
> Hi Arthur,
>
>
> On Tuesday 12 November 2013 12:39 PM, Arthur She wrote:
>
>> 2. By data migration
>> https://staging.review.linaro.o
Hi Arthur,
On Tuesday 12 November 2013 12:39 PM, Arthur She wrote:
2. By data migration
https://staging.review.linaro.org/#/c/321/5/lava_scheduler_app/migrations/0034_add_permission_cancel_resubmit_testjob.py
This method no need to modify lava-deployment-tool. The new permission
will take effect
Hi Senthil,
Sorry for the unclear commit message.
There are two approaches to add a new permission
1. By custom permissions
As it showed (
https://staging.review.linaro.org/#/c/321/5/lava_scheduler_app/models.py),
I removed it, because in order to apply new permission, we need to run
command "/sr
Hi Arthur,
I couldn't understand the commit message below. I could see that
migrations are broken due to this commit. Can you elaborate what should
be done here?
I usually run schemamigrations once I change something on the model, but
it is not working anymore due to the following commit.
