dolibarr-bugtrack
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dolibarr-bugtrack] [Bug #1363] Unable to update from 3.5.1 to 3.5.2


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #1363] Unable to update from 3.5.1 to 3.5.2
Date: Wed, 07 May 2014 15:06:55 +0200

Doliforge
Is this email not displaying correctly?
update email preferences.

Unable to update from 3.5.1 to 3.5.2

Latest modifications

2014-05-07 15:06 (Europe/Paris)
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.
Changes:
  • Resolution: 
NoneFixed

Answer now

Snapshot

 Details
Submitted by:  Marcos García (marcosgdf) Submitted on:  2014-05-01 15:43
Last Modified On:  2014-05-07 10:50 
Summary:  Unable to update from 3.5.1 to 3.5.2
Description:  URL http://dev.dolibarr.org/install/upgrade.php?action="">

Request 36 sql='ALTER TABLE llx_categorie_contact ADD CONSTRAINT fk_categorie_contact_categorie_rowid FOREIGN KEY (fk_categorie) REFERENCES llx_categorie (rowid);'
Error DB_ERROR_1022: ALTER TABLE llx_categorie_contact ADD CONSTRAINT fk_categorie_contact_categorie_rowid FOREIGN KEY (fk_categorie) REFERENCES llx_categorie (rowid);
Can't write; duplicate key in table '#sql-a32_169'

Request 37 sql='ALTER TABLE llx_categorie_contact ADD CONSTRAINT fk_categorie_contact_fk_socpeople FOREIGN KEY (fk_socpeople) REFERENCES llx_socpeople (rowid);'
Error DB_ERROR_1022: ALTER TABLE llx_categorie_contact ADD CONSTRAINT fk_categorie_contact_fk_socpeople FOREIGN KEY (fk_socpeople) REFERENCES llx_socpeople (rowid);
Can't write; duplicate key in table '#sql-a32_169'
Step to reproduce bug:  1. Fresh install (git checkout 3.5.1)
2. Initial config, enabled modules: thirds, invoices, products
3. Create product: PRODA
4. Create a client: "Client"
5. Create a prov invoice for "Client".
6. Update files (git checkout 3.5.2)
7. Install wizard is shown, choose to update 3.4.0 - 3.5.0 > 3.5.0
8. KO queries
Detected in version:  3.5.2 Category:  Core Problem
Severity:  9 - Blocking - Critical OS Type/Version:  
PHP version:   Database type and version:  5.6.17-1~dotdeb.1
 Status
Status:  Open Assigned to:  None
Resolution:  Fixed 

Comments

Laurent Destailleur 2014-05-07 15:06
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.
Marcos GarcĂ­a 2014-05-07 10:50
It worked! Thanks.
Laurent Destailleur 2014-05-06 21:59
This seems to be a problem with mysql 5.6. It introducs a new error code "1022".
Can you add this line
1022 => 'DB_ERROR_KEY_NAME_ALREADY_EXISTS',
into
$errorcode_map of file mysqli.class.php and mysql.class.php
then rerun process and tell if it fixes ?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]