Prochaines Sessions
Les prochaines formations et démonstrations sont ouvertes, inscrivez-vous rapidement !
Démonstration de ProjeQtOr(gratuit, sur inscription)
13 mai 2025 (10h30-12h) 5 juin 2025 (16h-17h30) |
Les prochaines formations et démonstrations sont ouvertes, inscrivez-vous rapidement !
Démonstration de ProjeQtOr(gratuit, sur inscription)
13 mai 2025 (10h30-12h) 5 juin 2025 (16h-17h30) |
installed in Dec 2016, constant automatic updates to recent version
I don't understand.I performed updates with distributed sql files starting with v4.0 by hand.
All scripts run like a charm, without any issue, through migration process.Those sql files are full of errors.
I don't find any.Especially wrong comment markers ('==text', '=== text') are found very often
No they don't (if run through migration process)Related sql statements fail for this
Our migration process, executing each script step by step, ensures that db structure is always the same, whatever version you come from and you go to.I recommend to introduce a check for proper db structure
For us, asap will be 2040 or later. We won't actually concentrate on this, as we have more urgent things in the roadmap.ASAP
Once again ,our migration process ensures this.to help keeping updated installations up to date and to ensure new installations are really working
That means you defined prefix for tables as ' ${prefix}' ?Table "${prefix}budgetelement" altered
Some errors on object User during migration process are "normal". You connect with new object structure but database is not latered yet.Error on SqlElement to get 'idLanguage' for Class 'User' : field 'idLanguage' not found in Database.
Ha, I was sure prefix starting with $ would lead to error....Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'a.${prefix}delivery' doesn't exist
2017-12-08 05:38:43.710 ***** ERROR ***** [V6.4.4] For query : ALTER TABLE `${prefix}delivery` ADD COLUMN `idProductVersion` INT(12) UNSIGNED DEFAULT NULL;
This is code of script that is not expected to be run manually..What you call ugly is original code from delivered sql files:
INSERT INTO `${prefix}workflow` (id,name, description, idle, workflowUpdate) VALUES
All works fineTry to run following sql in mysql (replace ${prefix} with real prefix):
--ADD BY TABARY Marc - 2017-06-06 - USE OR NOT ORGANIZATION BUDGETELEMENT
INSERT INTO `${prefix}parameter` (`parameterCode`, `parameterValue`) VALUES ('useOrganizationBudgetElement', 'NO');
DELETE FROM `${prefix}columnselector` WHERE `objectClass` = 'Organization';
DELETE FROM `${prefix}filter` WHERE `refType` = 'Organization';
--END ADD BY TABARY Marc - 2017-06-06 - USE OR NOT ORGANIZATION BUDGETELEMENT
mantenance.php is tested on each version, for migration and for first install.Check your parser in maintenance*php files as well. It SHOULD skip comments but, especially statements like this example have caused issues in db. Otherwise there should have been many more error messages when running sql manually.
Once aign, you MUST NOT run scripts ma,nually.Otherwise there should have been many more error messages when running sql manually.
But if first install was done manually, it is sure source of errors.After first installation all upgrades have been performed by your software in automatic mode. Reason to run those sql statements by hand are errors quoted from log. There have been a lot of statements since v4.0 which didn't cause an error (even "create table" statements!). Therefor the automatic process is error prune to some extend Otherwise it couldn't give a message about missing field or even a missing table in db.
DB name=a and prefix=${prefix}"a" is db name which is written to log file.
I really don't.Why do you try to call other people stupid?
I guess there is somethong wrong in definition of prefix a"2017-12-08 05:38:43.203 ===== TRACE ===== Table "${prefix}ticket" altered."
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.