spacemanspiff2007

This is what is generated by aerich: ```sql -- upgrade -- ALTER TABLE "mymodel" DROP COLUMN "myfield"; -- downgrade -- ALTER TABLE "mymodel" ADD "myfield" JSON; ``` The generation is...

It's creating the .ini file and the models in the .migrations folder just fine. I then move my app (including the .ini and migration files but without the .db file)...

``pip install tortoise-orm``

I'm having the same issue with ``aerich 0.5.5``. I'm however adding a JSON field. It seems it's enough if there is a m2m field.

I too think that this adds way too much complexity without providing enough benefit. Persisting forecasts/historic states is something that can easily be done in rules/through the REST API (see...

> > Persisting forecasts/historic states is something that can easily be done in rules/through the REST AP > > I don't think a binding should be forced to use the...

@jbaudisch What exactly are you interested in? The date when the event was emitted or the date when the item updated the state? Since you are using the jsons I'm...

That's a great idea @digitaldan. Since the data has to be stored anyway why not use a DB from which the data can also be directly consumed from. Another option...

> Association of item and metadata is loosely coupled ... and it builds some kind of race condition especially during startup of the system when items and metadata could be...

Thank you for your detailed explanation - I understand it a little bit better now. > I do have items which use state description and some additional namespaces I use...