Polypheny-DB
Polypheny-DB copied to clipboard
polypheny
A self-adaptive Polystore that provides cost- and workload aware access to heterogeneous data.
It is currently not possible to update labels of an information element of type graph.
Due to foreign key constraints, it would be possible to already prefill the join operator with appropriate data.
It is not possible to connect columns in the UML view on a tablet. Already existing relations are displayed correctly. In the Query Plan Builder, it is not possible to...
Add support for exporting query analyzer sessions to a file. This would allow to send it to a developer in case of a bug.
The suggestions should be more context-dependent (only suggest a column name if it is allowed and expected at this place in the query).
Currently it is only possible to model aggregation functions in the query plan builder. Other functions like `abs`, `distance` or `sqrt` are not possible. Functions can have a different number...
Implement a drag-and-drop based management view for configuring data vertical partitioning, horizontal partitioning and replication.
Add a button in the right menu which opens a dedicated window showing the camera stream, the recognized gestures and additional instructions. It should be possible to deploy, run and...
Allow to export the current schema (or parts of it) as PolySQL-Script. It should be possible to select whether the export should include the currently stored data. The UI should...
It should be possible to open the logical query plan from the query analysis in the plan builder. This would allow to easily change complex query plans without needing to...