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
--
You received this message because you are subscribed to the Google Groups
"tryton-dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton-dev/7346ef4e-1c3a-db69-7321-fec84fa0c7cf%40netbsd.org.
