resend:upgrade warnings with recent develop branch

[Richard PALO]

[resend, g$ggle still broke, apparently]
full upgrade with recent 'develop' shows the following:
> 4815 140668832162880 [2017-05-01 16:35:10,058] WARNING trytond.backend.postgresql.table Unable to set column company of table account_fiscalyear_invoice_sequence not null !
> Try to re-run: trytond.py --update=module
> If it doesn't work, update records and execute manually:
> ALTER TABLE "account_fiscalyear_invoice_sequence" ALTER COLUMN "company" SET NOT NULL
>

Indeed I have 25 records where company is not set here (single company db).

Is this a case where I need to manually set the company (id=1), or is
it a possible omission in the migration code to check?

I see as well:
> 4815 140668832162880 [2017-05-01 16:35:29,739] INFO trytond.convert Deleting 5...@ir.property from account_payment.property_payment_group_sequence
> 4815 140668832162880 [2017-05-01 16:35:29,739] WARNING trytond.convert Could not delete id 58 of model ir.property because model no longer exists.
> 4815 140668832162880 [2017-05-01 16:35:29,760] INFO trytond.convert Deleting 5...@ir.property from product.property_cost_price_method
> 4815 140668832162880 [2017-05-01 16:35:29,761] WARNING trytond.convert Could not delete id 57 of model ir.property because model no longer exists.
> 4815 140668832162880 [2017-05-01 16:35:29,761] INFO trytond.convert Deleting 1...@ir.property from product.property_product_cost_price_method
> 4815 140668832162880 [2017-05-01 16:35:29,762] WARNING trytond.convert Could not delete id 1 of model ir.property because model no longer exists.
> 4815 140668832162880 [2017-05-01 16:35:29,773] INFO trytond.convert Deleting 2...@ir.property from party.property_party_sequence
> 4815 140668832162880 [2017-05-01 16:35:29,774] WARNING trytond.convert Could not delete id 2 of model ir.property because model no longer exists.

Not clear if these can simply be deleted or not.
> id | create_uid | create_date | res | value | write_uid | field | write_date | company
> ----+------------+----------------------------+-----+---------------+-----------+-------+------------+---------
> 1 | 0 | 2015-03-22 04:43:04.18063 | | ,fixed | | 732 | |
> 2 | 0 | 2015-03-22 04:44:17.036349 | | ir.sequence,1 | | 909 | |
> 57 | 0 | 2016-05-06 17:12:16.543205 | | ,fixed | | 732 | |
> 58 | 0 | 2016-05-07 03:53:08.345128 | | ir.sequence,4 | | 2404 | |
> (4 lignes)

I noticed that there are two other records with a null 'res', namely for the default client and supplier accounts
in account.account. I guess I presume they are okay but should there be some value set for 'res'?
Something like 'party.party,1' which is the party id of the company?

Cheers,
--

Richard PALO

--
Richard PALO

[Cédric Krier]

On 2017-05-01 22:39, Richard PALO wrote:
> [resend, g$ggle still broke, apparently]
> full upgrade with recent 'develop' shows the following:
> > 4815 140668832162880 [2017-05-01 16:35:10,058] WARNING trytond.backend.postgresql.table Unable to set column company of table account_fiscalyear_invoice_sequence not null !
> > Try to re-run: trytond.py --update=module
> > If it doesn't work, update records and execute manually:
> > ALTER TABLE "account_fiscalyear_invoice_sequence" ALTER COLUMN "company" SET NOT NULL
> >
>
> Indeed I have 25 records where company is not set here (single company db).
>
> Is this a case where I need to manually set the company (id=1), or is
> it a possible omission in the migration code to check?

I'm pretty sure it is because you are migrating between two development
versions. We do not support such migration, only between releases.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[Richard PALO]

Le 03/05/2017 à 10:12, Cédric Krier a écrit :
> On 2017-05-01 22:39, Richard PALO wrote:
>> [resend, g$ggle still broke, apparently]
>> full upgrade with recent 'develop' shows the following:
>>> 4815 140668832162880 [2017-05-01 16:35:10,058] WARNING trytond.backend.postgresql.table Unable to set column company of table account_fiscalyear_invoice_sequence not null !
>>> Try to re-run: trytond.py --update=module
>>> If it doesn't work, update records and execute manually:
>>> ALTER TABLE "account_fiscalyear_invoice_sequence" ALTER COLUMN "company" SET NOT NULL
>>>
>>
>> Indeed I have 25 records where company is not set here (single company db).
>>
>> Is this a case where I need to manually set the company (id=1), or is
>> it a possible omission in the migration code to check?
>
> I'm pretty sure it is because you are migrating between two development
> versions. We do not support such migration, only between releases.
>

I am pretty sure that this base was always on a released version since creation (03/2015) which
I believe was on 3.4. It is only very recently, after 4.2 in waiting for last few bits for 4.4
(which has subsequently been released) that it is on the trunk master.

The questions remain, though, as to the rectification needed.

--
Richard PALO