Skip to content

Conversation

@LukasFehring
Copy link
Collaborator

@LukasFehring LukasFehring commented May 9, 2025

Description

Motivation and Context

Changes

Type Of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

How has This Been Tested?

  • Database provider: MySQL and sqlite
  • Python version: 3.9.18
  • Operating System: linux, mac, windows

Does this Close/Impact Existing Issues?

Checklist

  • My change is based on the latest stage of the develop branch.
  • My change required a change of the documentation, which has been done.
  • I checked that the documentation can be build, visualizes everything as expected, and does not contain any warnings.
  • I have added/adapted tests to cover my changes.
  • The tests can be executed successfully.
  • The notebooks can be executed successfully.
  • The notebooks can be executed with mysql as provider.
  • I have added a description of the changes to CHANGELOG.rst.

@LukasFehring LukasFehring linked an issue May 9, 2025 that may be closed by this pull request
@LukasFehring LukasFehring requested a review from mwever May 16, 2025 07:41
Copy link
Collaborator

@mwever mwever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG2M

@LukasFehring LukasFehring merged commit c86f7ea into develop May 16, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

get_table with condition

3 participants