Project

General

Profile

Anomalie #5540

Migration squiremail vers roundcube

Added by Francis Bordes almost 10 years ago. Updated over 7 years ago.

Status:
Ne sera pas résolu
Priority:
Normal
Assigned To:
-
Target version:
-
Start date:
Due date:
% Done:

10%

Spent time:
Distribution:
EOLE 2.3

Description

Lors du passage de squirremail à roundcube, il n'y a pas la reprise du carnet d'adresse personnel.

History

#1 Updated by Arnaud FORNEROT over 9 years ago

  • Project changed from Envole to roundcube

#2 Updated by Joël Cuissinat over 9 years ago

Table squirrelmail.address :

+-----------+--------------+------+-----+---------+-------+
| Field     | Type         | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| owner     | varchar(128) | NO   | PRI |         |       |
| nickname  | varchar(16)  | NO   | PRI |         |       |
| firstname | varchar(128) | NO   | MUL |         |       |
| lastname  | varchar(128) | NO   |     |         |       |
| email     | varchar(128) | NO   |     |         |       |
| label     | varchar(255) | YES  |     | NULL    |       |
+-----------+--------------+------+-----+---------+-------+

Le champ "owner" contient bien l'uid de l'utilisateur et les autres champs servent à décrire l'un de ses contacts.

#3 Updated by Joël Cuissinat over 9 years ago

  • % Done changed from 0 to 10

Table roundcube.contacts :

+------------+------------------+------+-----+---------------------+----------------+
| Field      | Type             | Null | Key | Default             | Extra          |
+------------+------------------+------+-----+---------------------+----------------+
| contact_id | int(10) unsigned | NO   | PRI | NULL                | auto_increment |
| changed    | datetime         | NO   |     | 1000-01-01 00:00:00 |                |
| del        | tinyint(1)       | NO   |     | 0                   |                |
| name       | varchar(128)     | NO   |     |                     |                |
| email      | text             | NO   |     | NULL                |                |
| firstname  | varchar(128)     | NO   |     |                     |                |
| surname    | varchar(128)     | NO   |     |                     |                |
| vcard      | longtext         | YES  |     | NULL                |                |
| words      | text             | YES  |     | NULL                |                |
| user_id    | int(10) unsigned | NO   | MUL | NULL                |                |
+------------+------------------+------+-----+---------------------+----------------+

Ici les problème est que "user_id" est une jointure vers la table "users" qui contient bien les utilisateurs cependant cette dernière est normalement peuplée dans un mode du type "auto-create".
=> vérifier si son peuplement manuel est possible

Table roundcube.users :

+-------------+------------------+------+-----+---------------------+----------------+
| Field       | Type             | Null | Key | Default             | Extra          |
+-------------+------------------+------+-----+---------------------+----------------+
| user_id     | int(10) unsigned | NO   | PRI | NULL                | auto_increment |
| username    | varchar(128)     | NO   | MUL | NULL                |                |
| mail_host   | varchar(128)     | NO   |     | NULL                |                |
| created     | datetime         | NO   |     | 1000-01-01 00:00:00 |                |
| last_login  | datetime         | YES  |     | NULL                |                |
| language    | varchar(5)       | YES  |     | NULL                |                |
| preferences | text             | YES  |     | NULL                |                |
+-------------+------------------+------+-----+---------------------+----------------+

#4 Updated by Joël Cuissinat over 9 years ago

mysql> insert into users (username)
    -> VALUES ('toto');
Query OK, 1 row affected, 1 warning (0.02 sec)

Semble OK, il faudra juste vérifier que l'initialisation du compte avec les valeurs par défaut ne pose pas de problème ultérieurement :)

#5 Updated by Arnaud FORNEROT over 7 years ago

  • Status changed from Nouveau to Ne sera pas résolu

la migration des comptes ne sera pas réalisée

Also available in: Atom PDF