Working with `Drift`

Hi,

I see that Drift adapter marked as WIP, but with extends LocalAdapter<T> I think we can make a DriftLocalAdapter<T extends DatumEntityInterface> at current state?

Can you give an example of how to work with Drift?

From what I understand about Datum after reading the docs the flow would be...

1. Create Drift models.
2. Create DatumEntity or RelationalDatumEntity models.
3. Create LocalAdapter for Drift and RemoteAdapter.

Questions

1. How do we handle migration between Drift and Datum?
2. Does Datum need to be aware of Drift schema changes, or is Drift fully responsible for migrations?

Start with the existing documentation for LocalAdapter, RemoteAdapter, and the Drift adapter's WIP status, then trace how DatumEntity and RelationalDatumEntity fit the proposed flow. Done means documenting a complete Drift usage example and clearly answering how migrations and Drift schema changes are handled.