You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, tree addresses are hardcoded in the main.rs file. The for this is:
We use Metaplex DAS' database and migrations written in sea-orm
LightDAS uses sea-orm as well
sea-orm maintains a table in the database about the applied migrations
If (1) applied some migrations, (2) cannot apply because when applying a migration, SeaORM checks the table and expects the older migration files to be present.
However, migrations of (1) and (2) cannot be together because they're altogether maintained by different teams i.e. Metaplex DAS team and LightDAS team
Figure out a way to apply migrations from LightDAS via SeaORM
The text was updated successfully, but these errors were encountered:
A possible fix to this is to skip using sea-orm for the trees table and directly have the create tree SQL commands in the code and run them directly on the db @KartikSoneji
Currently, tree addresses are hardcoded in the
main.rs
file. The for this is:sea-orm
sea-orm
as wellsea-orm
maintains a table in the database about the applied migrationsFigure out a way to apply migrations from LightDAS via SeaORM
The text was updated successfully, but these errors were encountered: