Project

General

Profile

Actions

Task #7545

open

Review SQLAlchemy vs Flask-SQLAlchemy consolidation options

Added by Pavel Kácha 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
01/06/2022
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

Actually we have three methods of database model definition and access.

  • Direct one for event database. We've already decided this doesn't change in #4628.
  • Flask-SQLAlchemy and some direct SQLAlchemy(*) access within Hawat.
  • Direct SQLAlchemy access(*) within Mentat - commandline tools and daemons.

Seems we could rewrite cmd utils to Flask CLI, benefiting from code simplification (probably even replacing/removing ZenScript parts of ZenKit). We would however still need some means to access Mentat configuration.

It might be harder for daemons (reporter for example).

So, the aim of this task is to review *SQLAlchemy usage, possibilities of consolidation (and removing the kludge to support both Hawat and Mentat apps) for informed decision and plan after.

No data to display

Actions

Also available in: Atom PDF