[yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

[Mark Hatle]

On 10/10/16 12:37 PM, Paul Eggleton wrote:
> On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote:
>>> On Oct 10, 2016, at 2:54 AM, Paul Eggleton <paul.eggleton at linux.intel.com>
>>> wrote:
>>>> On Fri, 07 Oct 2016 13:20:50 Mark Hatle wrote:
>>>> FYI, I have made sure these are re-based on top of paule/django18 and
>>>> pushed to:
>>>>
>>>> git://git.yoctoproject.org/layerindex-web mhatle/django18
>>>>
>>>> BTW for me upgrading from paule/django18 to this version.  I only had to
>>>> run 'manage.py syncdb'.
>>>>
>>>> This created the new database and added the missing field for the
>>>> recommend.> 
>>> I'm not sure how that worked there but it doesn't work here. If I take a
>>> database that works on paule/django18, run syncdb then open the admin
>>> interface and click on "Layer branches" I get:
>>
>> We found a severe lack of instructions for creating migrations.  There were
>> instructions for adding and deleting full DBs but not changing them.  We
>> will need pointers or help to resolve this.
>>
>>>  no such column: layerindex_layerbranch.collection
>>
>> I never got that, but I'm also running SQLite.  May be the difference.
> 
> I'm using sqlite here also.
>  
>>> I'm afraid we really do need to create migrations whenever we change the
>>> models.
>>
>> Based on your prior comments we failed to find ANY reasonable examples, docs
>> or instructions on doing this.  So we are stuck without help.
> 
> I'm happy to help directly if needed, but did you come across this already?
> 
>   https://docs.djangoproject.com/en/1.8/topics/migrations/

Unfortunately that is the exactly document I was looking at and could not figure
it out.

I can the various commands, makemigrations and related.. and the system simply
told me "no migrations necessary".. and didn't generate any.

So we were never able to figure out what a migration should look like or how to
generate it.

If you (or someone else) can help us figure out how to create a migration, I
suspect after the first one  ---  future ones will be much easier to generate.

--Mark


> Cheers,
> Paul
>