package dev ;

public class DevTDB
{
    // ** Release
    // TDB shutdown hook.
    
    // Check commands and use of --graph
    
    // ---- BulkLoader2
    // Stats while loading.
    // Tune sort --buffer-size=50%
    // Prefixes to be set during bulk loading 1 & 2
    
    // Extract a better set of factory operations, using the default names and sizes, 
    // for internal structures like B+Tress and NodeTable, and TupleIndexes.
    //   NodeTableFactory and SetupTDB.makeNodeTable have common code. 
    //   Remove NodeTableFactory and have one per-technology setup/maker
    
    // Abort long running query.
    // PrefixMapping = PrefixMap
    
    // ---- Documentation
    // http://openjena.org/wiki/TDB/JavaAPI#Concurrency
    // http://openjena.org/wiki/TDB/Concurrency
    // and ref to ARQ.
    // http://openjena.org/wiki/TDB/Assembler to document unionDefaultGraph
    
    // --explain.
    // http://openjena.org/wiki/TDB/Configuration
    // http://openjena.org/wiki/TDB/Optimizer
    // Update: http://openjena.org/wiki/TDB/Optimizer#Investigating_what_is_going_on
    
    // == Misc
    //    Tidy up wiki (esp "Use from java" - use datasets, show loader use)
    
    // ** Partial ranges : S P ?o , ?o start, ?o finish 
    
    // ** Advanced block work - free chain management.

    // =====
    // Enable FILTER assignment for strings (and numbers?) via dataset context setting?
    // -- Tuples
    // Interface, TupleFactory, TupleImpl
    // TupleMask (or TupleImpl itself has a length field?? TupleMask(T[] or Tuple<T>)) 
    // Sort : with colmap?
    // TupleSlice
    
    // ---- Pipeline
    // Weak inferencing (in query rewriting):
    // rdfs:subClassOf (aux table).
    // rdfs:subPropertyOf (aux table).

    // ---- Optimizer
    // Early truncation of patterns
    //  ?s <p> <foo> . ?s <q> ?v . ?s <r> ?x
    // Favour connected next triple pattern (but grounding makes this less relevant) 
    // If <r> has no solutions fall back to triple pattern 1
    // Just need to keep var -> first def mapping but all mentions may be useful. 
    // (Idea from Alisdair)
    
    // ---- NodeId:  
    // Bit 0: 0 - 63 bits of id (hash!) or block allocation for cluster.
    // Bit 0: 1 - inline
    // Schema compatibility needs to handle this carefully.
}