Skip to content

Bump org.hsqldb:hsqldb from 2.7.0 to 2.7.2#36

Closed
dependabot[bot] wants to merge 8 commits intomainfrom
dependabot/maven/org.hsqldb-hsqldb-2.7.2
Closed

Bump org.hsqldb:hsqldb from 2.7.0 to 2.7.2#36
dependabot[bot] wants to merge 8 commits intomainfrom
dependabot/maven/org.hsqldb-hsqldb-2.7.2

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github May 24, 2024

Bumps org.hsqldb:hsqldb from 2.7.0 to 2.7.2.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

julianhyde and others added 8 commits May 23, 2024 13:18
…ential integrity of names)

Add some semantic validation steps to the MiniLookml
validator, to serve as examples for people building real
validators.

We check name uniqueness (that you can't have a dimension
and a measure with the same name) and referential integrity
of names (that if a join references a view "v1", then there
must be a view named "v1" in the model).

In future, perhaps these constraints could be defined in the
schema; if so, the code could be removed from the validator.

Fixes #35
Allow the parser position (`class Pos`) to contain nested
positions.

This will allow us to generate multi-part positions for code
blocks. For example,

  sql_on: t1.c1 = t2.c2;;

yields a code-property value spanning the whole
"sql_on: t1.c1 = t2.c2;" but for detailed error reporting we
need to know the exact location of the nested SQL string
" t1.c2 = t2.c2".

Fixes #32
Validate SQL fragments in a model.

This step is called 'semantic validation', to distinguish it
from the previous 'schema validation' step.

Add class SqlValidator, powered by Calcite.

Add the embedded HSQLDB Steelwheels database as a dependency,
for testing.

Fixes #34
…perties are required

In schema, add a `cardinality` property (with values
"optional" or "required") to the property object, and enforce
it in the schema validator.

For example, if we add "cardinality: required" to
mini-lookml-schema, as follows:

  object_type: measure {
     property: type {
       type: measure_field_type
      cardinality: required
    }
    ...
  }

then the following model is now invalid:

  view: v1 {
    measure: x {
      type: count
    }
    measure: z {
    }
    dimension: y {}
  }

because measure "z" should have a "type" property.

Enforce property.cardinality in the schema validator;
in Mini-LookML, measure.type is now required.

Fixes #33
…re that properties are mutually exclusive

Allow schema to declare that particular properties of an
object are mutually exclusive using the new
`cardinality_constraint` property. For example, if we add

  cardinality_constraint: check_on {
    properties: [sql_on, foreign_key]
  }

to mini-lookml-schema, then the following view generates an
error that the same object cannot have both `foreign_key` and
`sql_on`.

  view: v1 {
  }
  explore: e {
    join: v1 {
      sql_on: true;;
      foreign_key: fk1
    }
  }

Fixes #31
Bumps org.hsqldb:hsqldb from 2.7.0 to 2.7.2.

---
updated-dependencies:
- dependency-name: org.hsqldb:hsqldb
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 24, 2024
@julianhyde julianhyde force-pushed the main branch 2 times, most recently from 8d1dbb7 to 10a974b Compare May 29, 2024 00:52
@dependabot @github
Copy link
Copy Markdown
Author

dependabot bot commented on behalf of github Jun 3, 2024

Superseded by #44.

@dependabot dependabot bot closed this Jun 3, 2024
@dependabot dependabot bot deleted the dependabot/maven/org.hsqldb-hsqldb-2.7.2 branch June 3, 2024 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant