تاریخچه Commit ها

نویسنده SHA1 پیام تاریخ
  eespie 393f93af38 N.1065 Fix performance issues. 7 سال پیش
  eespie d6efb4da03 N.1065 Fix performance issues. 7 سال پیش
  eespie fd52780b35 N°1110 - DataSynchro: PHP Notice Undefined Index 7 سال پیش
  eespie 8ead6cc149 N.1065 Fix performance issues. 7 سال پیش
  eespie c94c84183a N°1110 - DataSynchro: PHP Notice Undefined Index 7 سال پیش
  eespie 73cee604b2 N.1065 Fix performance issues. 7 سال پیش
  pgoiffon a82a7f1c3a N.1065 When joining, reverse leaf-root order : now it's root first ! 7 سال پیش
  romainq 0e026aeaee N.1065 and #372 Query build cache not efficient with global search (each search generates about 80 new entries in the APCu cache) 7 سال پیش
  eespie 280a10cb85 Code cleanup. 7 سال پیش
  eespie 9e56c1be9c N.1065 Fix performance issues (caches added on query build) 7 سال پیش
  romainq 0e1f3d02b9 Rework of the edition of 1-N and N-N links: managed as a delta from the GUI down to the the lowest APIs. 8 سال پیش
  romainq 5bb516195d N.897 Object having too many external keys could not be recorded (61 tables) 8 سال پیش
  romainq ff986c63aa Internal: DBObjectSearch->AddCondition, allow the case $value = null (otherwise failing because the keyword null has not yet been implemented in OQL) 8 سال پیش
  romainq b246164f18 Obsolescence: finalizing the implementation of the flag (hide obsolete objects, show an icon on hyperlinks and a tag on the object details, user preference defaulting to the new setting 'show_obsolete_data') 8 سال پیش
  romainq 4b36e9e017 Obsolescence: introduction of this new concept (wording could change later). The obsolescence of an object is computed after other attributes, by the mean of an OQL expression. The code has been refactored (again) so as to factorize between the computation of friendly names and the computation of obsolescence flags. The refactoring involved a significant AND RISKY change: external key friendly names (magic attributes) have been changed from AttributeFriendlyName to AttributeExternalField, which simplifies the SQL query build logic. 8 سال پیش
  romainq 3109a0a7ca Internal: 8 سال پیش
  glajarige 4988d1d8d7 Internal: OQL error reporting 8 سال پیش
  romainq 34ab6cd77b NEW! Archiving data. Archiving is a soft delete. It can be undone. Enter the archive mode to see all the data including archives (everything is read-only in that mode). Archiving must be enabled per class (data model). Archiving is achieved by the mean of the API DBObject::Archive (or Unarchive). 8 سال پیش
  romainq 5e615a435d N.718 (continuation) Audit failing with message "Attempting to merge a filter of class A with a filter of class B" (regression introduced in branch 2.3).... 8 سال پیش
  romainq dbbd1d4e56 N.718 Audit failing with message "Attempting to merge a filter of class A with a filter of class B" (regression introduced in branch 2.3). There are circumstances for which the queries cannot (yet) be optimized (fallback to the original algorithm) 8 سال پیش
  romainq 7711c1aeb7 N.539 Regression introduced in [r4451] on oct 7th. Some OQL were issuing a notice and some were generating a SQL query that would fail with error "Column 'functionalci_id' in where clause is ambiguous" (See CI details) 8 سال پیش
  romainq d43ef8ceb7 Continuing [r4488] N.536 Regression introduced in [r4469] (N.505), itself fixing a regression introduced in [r4404]. REQUIRES TESTING 8 سال پیش
  romainq f58c412702 N.536 Regression introduced in [r4469] (N.505), itself fixing a regression introduced in [r4404]. REQUIRES TESTING 8 سال پیش
  romainq ad34ae5628 N.505 Regression introduced in [r4404]. Security issue - Object visibility totally screwed the APC cache (user data) is enabled. This is a change in the way SQL queries are built and therefore requires testing. 8 سال پیش
  romainq 8fd191860b N.434 ... Continuation... Fixed regression introduced in [r4448]. OQL (parsed) queries are optimized too but the SQL query cannot be executed. See example herebelow: 8 سال پیش
  romainq 81cac08849 N.434 Optimized the DB queries. As an example, the query that shows the service catalog in the enhanced customer portal is now made of 5 nodes (at the class level) whereas it used to be made of 11 nodes... for the exact same results. This optimization impacts almost each queries built by iTop. The expected benefit can insignificant or not, depending on the cardinality of the data, the datamodel and the original OQL queries. We found one case where the query execution would apparently never end and it takes now less than a second. The risk with such a change is that is affects most of the queries built by iTop -requires testing! 8 سال پیش
  romainq c05b6818e5 N°436 Core API: Correctly (mathematically!) handle the "allow all data" flag, with UNIONS and INTERSECTIONS. Requires testing 8 سال پیش
  romainq 1d69c5f27c OQL: fixed an old limitation, hierarchies can now be expressed both ways. Example of a query that now works fine: SELECT Organization AS root JOIN Organization AS child ON child.parent_id BELOW root.id WHERE child.name LIKE 'Combodo'. In the previous implementation, the operator was interpreted as '='. 9 سال پیش
  romainq 99ec255431 Internal: DBSearch::Intersect to throw an exception whenever any of the merged queries have a queried class that does not correspond to the first joined class. This is a limitation of the current implementation of Intersect. Allowing such use cases would require quite a rework of that API. 9 سال پیش
  dflaven ccef399cfa Support of date and time custom formats... continuing towards the beta ! 9 سال پیش