Feature #1517
Feature #1511: Reporting v3
move to a completely database-backed approach to displaying the conversion artifacts (.cache, .lexer...)
Start date:
09/10/2012
Due date:
% Done:
70%
Estimated time:
16.00 h
billable:
No
vendor_id:
GCD
History
#1 Updated by Greg Shah over 11 years ago
- Target version set to Milestone 2
- Estimated time set to 16.00
#2 Updated by Greg Shah over 11 years ago
- Target version changed from Milestone 2 to 25
#3 Updated by Greg Shah over 7 years ago
- Target version changed from 25 to Reporting 3.0
#4 Updated by Eric Faulhaber over 6 years ago
- % Done changed from 0 to 70
- Status changed from New to WIP
Current status in FWD 3.1:
- Cache files and un-preprocessed external procedure source files are stored in the
rptdb
relational database and are served from there. - Lexer and parser views have been omitted intentionally from the v3 reporting implementation.
- AST files are still read from the file system. Ultimately, these probably should be stored in and served from a graph database.