 dflaven
|
67e80ac0ee
Pan and zoom in the impact analysis view.
|
9 years ago |
|
dflaven
|
5551f50e4e
Make sure that the SQL mutexes are specific to the current iTop instance, but still preserving the capability for the setup to detect an already running cron job with or without a valid config file.
|
10 years ago |
 romainq
|
8e646e72de
Enable queries on the synchronized objects (SynchroReplica::dest_id changed into an attribute of type AttributeObjectKey).
|
10 years ago |
|
dflaven
|
d045f63fb2
Oops, wrong commit, reverting these two files to their previous version.
|
10 years ago |
|
dflaven
|
610247a0cb
Enhancement: support injection of new modules treated as data.
|
10 years ago |
|
romainq
|
30c759983a
#1039 Continuation of the fix implemented in [3465] that introduced a stopper regression (Fatal Error)
|
10 years ago |
|
dflaven
|
4a57214936
#1039: prevent concurrent executions of either synchro_import.php or synchro_exec.php for a given data source, since it would lead to unpredictable results.
|
10 years ago |
|
dflaven
|
0271e09150
#1016: record the displayed value of the database_table_name field in the database.
|
10 years ago |
|
romainq
|
1fc608a082
#979 Data synchro: recover the DB triggers (backup/restore). I've tested various combinations of the previous check (new columns to synchronize) and the new one (missing triggers).
|
10 years ago |
|
romainq
|
a432a135ec
#854...ROLLBACK, undoing the commit [3185]. The implementation has been postponed to the next major relase.
|
11 years ago |
|
dflaven
|
17f4b02ee4
#944 Speed-up the display of CSV import history. IF the feature is enabled, the CSV import history is:
|
11 years ago |
|
romainq
|
78e1bcd149
#854 Flag Is null allowed not working on attributes Date and DateTime + the default value is now operant
|
11 years ago |
|
dflaven
|
1fe1a03719
Limit the display of the status to the latest 100 runs of the synchro data source.
|
11 years ago |
|
romainq
|
3c4bb1287f
#784 Data sync: display the attribute code (as well as its label in the user language)
|
11 years ago |
|
romainq
|
c059b10554
All the overloads of DisplayBareProperties must return an array (otherwise a warning is issued and field validation will not work as expected)
|
12 years ago |
|
romainq
|
40990c8e11
#692 Compensate the effect of this fix committed as 2705
|
12 years ago |
|
dflaven
|
7b776554c1
Fix for Trac #497: allow bulk modification of "duration" fields.
|
12 years ago |
|
romainq
|
eafa11ecfe
Updated copyright (2012) and license (LGPL changed to AGPL)
|
12 years ago |
|
romainq
|
34ede9dbde
CSV import/export reworked:
|
12 years ago |
|
dflaven
|
0d36b281fb
Enhancement: added a new (hidden) configuration setting 'synchro_prevent_delete_all' (default to true) to deactivate the "safety belt" and allow the deletion of all replicas of a synchro task in one go.
|
12 years ago |
|
dflaven
|
797486175f
Implemented Track #582: "stable name" for synchro_data_xxx tables.
|
13 years ago |
|
romainq
|
21fb95c5d9
#540 Data synchro: the option "write if empty" was not implemented
|
13 years ago |
|
dflaven
|
4ddb1ae304
Bug fix: to do not try to access a DataSource while it's being deleted
|
13 years ago |
|
dflaven
|
5dc9619b6c
Added detecting of missing columns in the synchro_data_xxx tables (in case of duplicate SQL column names in the orignal data model). See Trac #503.
|
13 years ago |
|
dflaven
|
f44dc2c721
Make sure that the creation of the data_synchro_xxx tables uses the utf8 charset and collation and the same DB Engine as the rest of the database.
|
13 years ago |
|
romainq
|
c0062afe9c
#509 Error in the display of a replica not yet synchronized
|
13 years ago |
|
dflaven
|
522405f5ff
Protects against a JS error while the synchro is running in chunk mode
|
13 years ago |
|
romainq
|
d084850b55
Synchro: fixed issue in the counter (deletion of replicas) and improved the behavior in case of an error happening in the underlying process
|
13 years ago |
|
romainq
|
88919ffcc6
Synchro: need to order the replicas by id for the split algorithm to work fine
|
13 years ago |
|
romainq
|
19d0f7f341
Synchro: keep track of the memory usage peak (SynchroLog), should the synchro be executed at once or in several steps
|
13 years ago |
