|
From: | Laurent Destailleur (eldy) |
Subject: | Re: [Dolibarr-dev] Migration from v2.9.0 to v3.1.0 - patch proposal |
Date: | Sun, 15 Jan 2012 23:22:19 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111229 Thunderbird/9.0 |
OK, i found the patch (it was just attached). For error Information sur le dernier accès en base en erreur: Unknown column 'fk_element' in 'where clause' It should not appears because the field is created by the 3.0.0-3.1.0.sql scriptsDo you have this field fk_element into llx_acitoncomm table now ? If not do you have a field note into llx_actioncomm ? Le 15/01/2012 10:06, Fernando Lagrange a écrit : Hello all, as this is my first post, let me quickly present myself: I am part of Demo-TIC, a structure that uses, creates and promotes Free Software. We use Dolibarr since version 2.9.0, mainly for invoices, proposal and structure's membership. Dolibarr is very useful and always improving, which is great to see and a pleasure to mention. :-) With version 3.1.0 being released, I've updated our testing installation from v2.9.0 to v3.1.0, following documentation and using our production database. All went smoothly on 2.9.0 to 3.0.0 update. But on 3.0.0 to 3.1.0 two errors popped up on data migration (see '3.0.0-3.1.0_data_migration_error' attached file). Looking at upgrade process, it appeared that this was due to 2.9.0-3.0.0.sql and 3.0.0-3.1.0.sql scripts. 2.9.0-3.0.0.sql contains some comment lines starting with "--" that are not followed by a space (mandatory following space is a mysql regression bug, and I've seen that almost all of these lines have already been corrected). 3.0.0-3.0.1.sql contains updates that made errors (unknown tables, columns, and indexes, impossible for mysql to find meaning of __DECRYPT('name')__ and so on). So that you'll find a patch made upon latest git 3.1 branch of Dolibarr. (Note that I did not removed last "insert into llx_c_actioncomm…" lines, even though they were not needed on my installation.) Can you please take attached git patch into account ? Before looking deeper, I also wanted to know if this is normal behaviour: mysql sql migration scripts made errors but upgrade process do not alert administrator !?! Keep up the good work ! Regards, -- Eldy (Laurent Destailleur). --------------------------------------------------------------- EMail: address@hidden Web: http://www.destailleur.fr Dolibarr (Project leader): http://www.dolibarr.org To make a donation for Dolibarr project via Paypal: address@hidden AWStats (Author) : http://awstats.sourceforge.net To make a donation for AWStats project via Paypal: address@hidden AWBot (Author) : http://awbot.sourceforge.net CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net |
[Prev in Thread] | Current Thread | [Next in Thread] |