Can we do away with the schema.json file?

jamie commented

2020-03-26 23:20:16 +00:00

(Migrated from git.hazaar.io)

This file is used to create an initial database, but it can pretty much be recreated at an point from the migration files. Without it, we might be better able to handle source merging. This would be because we may be able to replay individual merges out of order. I'd like to write some code that builds the schema file from migration files instead of reading it from disc. Then play around and see if we can get replays to replay migration scripts out of order.

jamie commented

2020-03-26 23:20:23 +00:00

(Migrated from git.hazaar.io)

changed title from Can we do away with the schema.json file to Can we do away with the schema.json file{+?+}

changed title from **Can we do away with the schema.json file** to **Can we do away with the schema.json file{+?+}**

jamie commented

2020-03-31 07:09:23 +00:00

(Migrated from git.hazaar.io)

created merge request !21 to address this issue

jamie commented

2020-03-31 07:09:23 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !21

jamie commented

2020-03-31 11:02:28 +00:00

(Migrated from git.hazaar.io)

closed via merge request !21

jamie commented

2020-03-31 11:02:28 +00:00

(Migrated from git.hazaar.io)

mentioned in commit ba21fcf32e

mentioned in commit ba21fcf32e6104578db596b4d82f7009bd39d4d9

jamie commented

2020-03-31 11:03:16 +00:00

(Migrated from git.hazaar.io)

Done! The schema file is no longer used! In fact we now only use the migration files to build the schema internally without the need for a schema file.

Rows
Columns

Can we do away with the schema.json file? #49