Skip to content

Unify model. Do not decide between Kdb1 or 2 based on object modle but on features #5

Description

@mstarke

The data model now is hard-chosen on load and cannot be modified. It's far more elegant to use a single Kdb2 like structure and import Kdb1 files into this model. On save it's possible to store in Kdb1 or 2 format.

If the user wants to use features not possible in Kdb1 files, there should be a warning in the GUI to inform, that this will result in a new database format, incompatible to the old one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions