Project

General

Profile

Feature #1759

design a database to back all TRPL processing

Added by Greg Shah over 11 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Database Backed Storage
Start date:
Due date:
% Done:

0%

Estimated time:
80.00 h
billable:
No
vendor_id:
GCD

Related issues

Blocks Conversion Tools - Feature #1758: design a database schema to contain a complete conversion project New
Blocks TRPL - Feature #1755: implement database-backed filtering/walking optimization New

History

#1 Updated by Greg Shah over 11 years ago

  • Subject changed from implement full database backing for TRPL to design a database to back all TRPL processing
  • Estimated time changed from 60.00 to 40.00

This must all complete TRPL processing solely from a database. The following features are expected to be needed:

1. A replacement for flat files. There must be a way to store files in the database (1 line in a file = 1 row in a table?) such that the file system does not need to be read/written to directly in order to read/write or otherwise process source files. In some ways, TRPL will provide a file system that is database backed.

2. storage/access to ASTs instead of file-system based XML

3. configuration

4. tracing, logging and errors

5. versioning

#2 Updated by Greg Shah over 11 years ago

  • Target version set to Code Improvements

#3 Updated by Greg Shah over 7 years ago

  • Estimated time changed from 40.00 to 80.00
  • Target version changed from Code Improvements to Database Backed Storage

Also available in: Atom PDF