khz

@nicolaiarocci @funkyfuture , @Flargebla Hi, since I was thinking about this combination (cerberus/dataclasses) as well, I stumbled upon this proposal and made a first approach that: - is a Validator...

Adapt method call to new naming convention for SQLAlchemy > 1.4.x (aka 2.0 API)

Something like: ``` if getattr(self.__class__,'_use_pow_schema_attrs', False): self.basic_schema = { "_uuid" : { "type" : "string", "default" : str(uuid.uuid4()) }, #"eid" : { "type" : "string" }, "created_at" : { "type"...

Need to check the SQLAlchemy changelog. SQLAlchemy has implemented some big API, Package naming and usage changes. Versoin 1.4.x => is the way to SQLAlchemy 2.0 See the => [SQLAlchemy...

Need to check DeclarativeBase class changes between 1.4.10 and 1.4.11

I checked the unversioned requirements. ``` dash dash-core-components dash-html-components dash-renderer dash-table dash-daq pandas numpy ``` **Leads to:** (As of 07 Feb 2020) ``` dash==1.9.0 dash-core-components==1.8.0 dash-daq==0.3.3 dash-html-components==1.0.2 dash-renderer==1.2.4 dash-table==4.6.0 ```...

Hi, I will be checking this.

This is due to some major changes in sqlalchemy 2.0. As a quick fix: in your virtual environment: `pip uninstall sqlalchemy ` `pip install sqlalchemy==1.4.46` `pip freeze` should show you...

can you check if the sqlqlchemy version was causing the issue ?