Skip to content

Support orm-loader >0.4.0 #13

@nicoloesch

Description

@nicoloesch

Motivation

With the new changes of orm-loader regarding more efficient loading and removal of psycopg2, we introduced a change of the backend API. As a result, we are currently capping the omop-alchemy<=0.6.2.

This change would allow continuous development and integration of continuous changes in omop-alchemy and orm-loader.

Pitch

  1. Validate the impact of the orm-loader changes, including the effect on omop-alchemy as its downstream package.

  2. Include potential changes that would affect this package

  3. Bump version requirement to the newest version of omop-alchemy

Alternatives

None. We need to keep including newer features and don't want to be held back.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions