Apache OpenOffice (AOO) Bugzilla – Issue 83250
DataPilot: refactor backend data access to use cache table
Last modified: 2013-08-07 15:15:24 UTC
We will switch to using cache table to cache the original data to avoid multiple scanning of source data, which is expensive especially for external database data. We will also simplify the current data access code by making effective use of the cache table implementation. This work is on-going in koheidatapilot01 CWS.
accepting the issue.
Setting target to 3.0.
fixed in koheidatapilot01.
re-assigning to oc for QA.
verified in cws
The options "Ignore empty rows" and "Identify categories" no longer work. These aren't the most important options, but they are there, so they must work. "Drill down" on a data field is a bit different from what it was in 2.4: - In 2.4, group columns were fully usable, so one could view the data for the subtotal of a group (see attached file). This wasn't specified explicitly, but it's always problematic to remove something that once worked. You should at least check if this can be added to your implementation without too much effort. - If a column/row field contains numeric entries, comparison should be done on the values (and was in 2.4). Otherwise, entries with different number formats might not be recognized, an example is also in the attached file.
Created attachment 52685 [details] Example for the drill-down problems
reopened because of above mentioned regression
back to development
@nn: thanks for the regression report. I just got back from Prague so I'll be little tied up for the next few days, but I'll look into this.
>The options "Ignore empty rows" and "Identify categories" no longer work. These aren't the most important options, but they are there, so they must work. This is fixed, and now should work. >- In 2.4, group columns were fully usable, so one could view the data for the subtotal of a group (see attached file). This wasn't specified explicitly, but it's always problematic to remove something that once worked. You should at least check if this can be added to your implementation without too much effort. This was a bit of work, but it should work now. I hope I got it right in all cases. >- If a column/row field contains numeric entries, comparison should be done on the values (and was in 2.4). Otherwise, entries with different number formats might not be recognized, an example is also in the attached file. This should also work. I now use ScDPItemData instead of plain-old String class to carry the data around. Let me know if there are still cases where it fails. All fixes are checked in to koheidatapilot01 cws.
RESOLVED FIXED once again.
back to oc for QA.
forgot to reopen for QA.
setting the status to FIXED
verified in internal build cws_koheidatapilot01
closed because fix available in builds OOO300_m6 and DEV300_m31