Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/major-opa
  • advisory/tj
  • main default protected
  • defect/telem
  • docs/pattern
  • spike/go-tools-124-gql
  • spike/go-tools-124
  • chore/deepmap
  • docs/mas
  • build/notify
  • fix/du
  • defect/diff
  • defect/json
  • chore/schema
  • feat/diff-json
  • chore/typo
  • build/binaries
  • build/changelog-
  • defect/otel
  • chore/otel
  • v0.116.2 protected
  • v0.116.1 protected
  • v0.116.0 protected
  • v0.115.3 protected
  • v0.115.2 protected
  • v0.115.1 protected
  • v0.115.0 protected
  • v0.114.0 protected
  • v0.113.5 protected
  • v0.113.4 protected
  • v0.113.3 protected
  • v0.113.2 protected
  • v0.113.1 protected
  • v0.113.0 protected
  • v0.112.0 protected
  • v0.111.1 protected
  • v0.111.0 protected
  • v0.110.2 protected
  • v0.110.1 protected
  • v0.110.0 protected
40 results

preflightchecks.go

Blame
  • Jamie Tanna's avatar
    825e0739
    chore: use `compatible_since` to perform compatibility validation · 825e0739
    Jamie Tanna authored
    To better provide insight for customers as to whether the version of
    DMD's tools can be used with a given version of a database, as well as
    whether their SQL queries may work as-is, we can use the
    `compatible_since` metadata.
    
    This falls back to the existing compatibility heuristic - of checking if
    there is an exact match between the CLI version in the database, and the
    version of the tool in use - which is fairly naive.
    
    In the case that `compatible_since` is present, we should present it to
    the user, even if we can't validate whether `IsCompatible`.
    
    As part of #532.
    825e0739
    History
    chore: use `compatible_since` to perform compatibility validation
    Jamie Tanna authored
    To better provide insight for customers as to whether the version of
    DMD's tools can be used with a given version of a database, as well as
    whether their SQL queries may work as-is, we can use the
    `compatible_since` metadata.
    
    This falls back to the existing compatibility heuristic - of checking if
    there is an exact match between the CLI version in the database, and the
    version of the tool in use - which is fairly naive.
    
    In the case that `compatible_since` is present, we should present it to
    the user, even if we can't validate whether `IsCompatible`.
    
    As part of #532.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.