Open mvorisek opened 4 years ago
@DarkSide666, @romaninsh Help wanted, wdyt?
That could be useful of course, but probably will not be that easy to implement because we don't define indexes (especially compound ones) anywhere in agile data. So there is no source of information for schema to work with.
That could be useful of course, but probably will not be that easy to implement because we don't define indexes (especially compound ones) anywhere in agile data. So there is no source of information for schema to work with.
For start it will be enought to be able to define them after the table is modelled (with setModel
or manually or imported).
Yes probably.
I'm not hoping that atk/schema will be completely looseless converter from data model to DB structure and back. Especially if we want to support other DB persistences like Oracle, NoSQL etc. Each DB engine does something differently. Even multiple same engine versions have quite big differences sometimes...
Single and compound indexes should be supported.