Fixes for using PostgreSQL

[matrss]

Created enum types should also be dropped on downgrade. Dropping tables must be committed to become visible.

Purpose of PR?:

Fixes #

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Does this PR results in some Documentation changes?
If yes, include the list of Documentation changes

Checklist:

• Bug fix. Fixes #
• New feature (Non-API breaking changes that adds functionality)
• PR Title follows the convention of <type>: <subject>
• Commit has unit tests

[ReimarBauer]

I expect that his works. I can verify this again later when we have merged both to develop.

[ReimarBauer]

I just looked into the model definition: "message_type"

[matrss]

The column that uses the type is called message_type, but the enum type in the database is created with the name messagetype. You can see that here:

MSS/mslib/mscolab/migrations/versions/92eaba86a92e_to_version_8_3_5_initial_migration.py

Line 61 in c602415

sa.Column('message_type', sa.Enum('TEXT', 'SYSTEM_MESSAGE', 'IMAGE', 'DOCUMENT', name='messagetype'), nullable=True),

, the relevant part being name='messagetype'.

[matrss]

I think it derives that name from simply lowercasing the class name of the enum defined here:

MSS/mslib/mscolab/message_type.py

Line 28 in c602415

class MessageType(enum.IntEnum):

[ReimarBauer]

I think it is "message_type" please double check

[ReimarBauer]

ok, thx.