sebastiendaniel / relational-json Goto Github PK

A pre-compiled, browser-based example, allowing users to play with relational-json directly, on an existing schema.

both properties theoretically only need the tableName of the relation, since the relation is always PK to PK.

Allow getting a defined list of objects instead one or all.

The get(); method of each table should accept an infinite amount of integer values against which to match PK values of it's objects, and return an array containing all those objects.

• get(x) would return the object itself, or undefined
• get(x1, x2, ..., xn) would return [ obj1, obj2, ..., objn ] or an array of the found items, or undefined if none are found.
• get() would return the current array of data.

put() breaks the inheritance structure by deleting and not re-creating children.

Passing "fullModel" around gives too much information for each method.
Ideally, each table will have its own "model", and each model is a node in a graph, with relations to other nodes (models).

That way, all methods can always work on a model, and jump to the next model without having to know about the fullModel.

profiling of data modification showed roughly a 30% increase in processing time when a DB has a preprocessor function. This excess excludes additional processing done by the function itself. The function we used was:

var preprocessor = function(tableName, field, value) {
  return value;
}

Not sure how this can be optimized, yet.

Extends and ExtendedBy and Aggregates need to use the same property names (foreignTable, foreignField, localTable, localField)