 eespie
|
6f6ec87c09
N°870: Bulk operation and obsolescence flag
|
7 anos atrás |
 romainq
|
d87bfaada7
Archive: Experimental API DBSearch::DBBulkWriteArchiveFlag, to quickly archive a huge number of objects (minimizes the number of queries needed to do the job, skips object change handlers, and DOES NOT RECORD the change in the history of object changes -that limitation could be fixed later)
|
8 anos atrás |
|
romainq
|
a83c24beec
Obsolescence: do not lose external keys pointing to obsolete data
|
8 anos atrás |
|
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 anos atrás |
|
romainq
|
d998853c23
Archives: refactoring of the API to enable/disable the archive mode
|
8 anos atrás |
|
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 anos atrás |
|
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 anos atrás |
|
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 anos atrás |
|
romainq
|
c05b6818e5
N°436 Core API: Correctly (mathematically!) handle the "allow all data" flag, with UNIONS and INTERSECTIONS. Requires testing
|
8 anos atrás |
|
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 anos atrás |
|
romainq
|
0064a82cd2
Fixed regression introduced with [3912] : autocomplete not working (new User request with lots of existing user requests)
|
9 anos atrás |
 glajarige
|
682a9c7b5d
DBSearch : Allow join between DBUnionSearch by adding the DBUnionSearch::Join verb
|
9 anos atrás |
|
romainq
|
3c7638bf00
Exclude magic parameters when listing query parameters (refactoring from run_query) This enables the use of magic parameters in the exports. The issue was less exposed in iTop 2.2.0 because only one single magic parameter was available.
|
9 anos atrás |
|
romainq
|
1d4c9abbfe
Prerequisites for custom fields
|
9 anos atrás |
|
romainq
|
1c5dc468d5
Magic query arguments:
|
9 anos atrás |
|
glajarige
|
2634b14e39
Core : Added CloneWithAlias function to DBSearch class. It creates a new DBObjectSearch from a DBSearch with a new alias.
|
9 anos atrás |
|
romainq
|
5f0de18ba6
Core API: added DBSearch:SetSelectedClasses
|
9 anos atrás |
 dflaven
|
cda7f3861f
Code refactoring to make the OQL parsing self contained in the "oql" subdirectory.
|
9 anos atrás |
|
romainq
|
b2618d03ae
Exports further improved:
|
9 anos atrás |
|
romainq
|
7645488c0d
Optimization: improved the OQL cache:
|
10 anos atrás |
|
romainq
|
5ed735e8d0
#942 OQL now supporting unions. Unions support polymorphism and can be used anywhere in the application.
|
10 anos atrás |
