View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Supportez nous sur Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Cancel changes by restoring historized data and some others remarks on "history" - ProjeQtOr

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)

 
 

Planifiez avec ProjeQtOr

14 et 15 mai 2025 (9h-12h30)

18 et 19 juin 2025 (9h-12h30)

 
 

Administrez avec ProjeQtOr

20 et 21 mai (9h-12h30)

25 et 26 juin (9h-12h30)

 

 

 

Cancel changes by restoring historized data and some others remarks on "history"

More
31 Juil 2014 10:06 #1 by Jean-Luc
There is an history of changes for every update. Excellent !
But this seems to be only a "for memory" info.

1. The possibility to cancel the last update by restoring the previous value stored in "history" would be very useful.

2. So the possibility to clean the "history" data (even only by an administrator), p.e. on oldest dates, could avoid to have finally an huge table !
(At the present time, the only possibility is to execute an SQL statement, p.e. in phpmyadmin…)

3. When we change ONE word in a big note (several thousands of characters), the whole note is historized. That is almost without utility. So, for big fields as varchar(4000) and text (that I implemented successfully, having some data >30 Kchars to migrate), history should only register effective changes (p.e. as done by "diff" utility).

Please Connexion or Create an account to join the conversation.

More
31 Juil 2014 11:27 #2 by protion

Please Connexion or Create an account to join the conversation.

More
31 Juil 2014 15:19 #3 by babynus

1. The possibility to cancel the last update by restoring the previous value stored in "history" would be very useful.

request recorded as Ticket #1484

2. So the possibility to clean the "history" data (even only by an administrator), p.e. on oldest dates, could avoid to have finally an huge table !

request recorded as Ticket #1485

3. When we change ONE word in a big note (several thousands of characters), the whole note is historized. That is almost without utility. So, for big fields as varchar(4000) and text (that I implemented successfully, having some data >30 Kchars to migrate), history should only register effective changes (p.e. as done by "diff" utility).

request recorded as Ticket #1486

Babynus
Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

More
04 Aoû 2014 13:33 #4 by climb4fun
Hi Jean-Luc,

yes - great idea :)
Thx.

Klaus

Please Connexion or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.039 seconds

Paramétrages de cookies

×

Cookies fonctionnels

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.

Session

Veuillez vous connecter pour voir vos activités!

Autres cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.