这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@0x777
Copy link
Member

@0x777 0x777 commented Sep 28, 2018

Fix migration logic to accommodate for non superuser permissions. Closes #567

Description

What component does this PR affect?

  • Server
  • Console
  • CLI
  • Docs
  • Community Content
  • Build System

Requires changes from other components? If yes, please mark the components:

  • Server
  • Console
  • CLI
  • Docs
  • Community Content
  • Build System

Related Issue

#567

Solution and Design

By clearing the hdb_views schema of existing views and functions instead of dropping and creating it again.

Type

  • 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)
  • Docs update
  • Community content

Checklist:

  • I have read the contributing guide and my code conforms to the guidelines.
  • This change requires a change in the documentation.
  • I have updated the documentation accordingly.
  • I have added required tests.

@0x777 0x777 requested a review from rakeshkky September 28, 2018 10:07
@shahidhk shahidhk changed the title do no clean hdb_views by dropping and creating the schema, closes #567 do not clean hdb_views by dropping and creating the schema (closes #567) Sep 28, 2018
@shahidhk shahidhk added c/server Related to server k/bug Something isn't working labels Sep 28, 2018
@shahidhk shahidhk merged commit b084249 into master Sep 28, 2018
@hasura-bot
Copy link
Contributor

Review app https://hge-ci-pull-568.herokuapp.com is deleted

@shahidhk shahidhk deleted the issue-567-alpha21-migration branch September 28, 2018 10:53
hasura-bot pushed a commit that referenced this pull request May 13, 2024
…ve` (#568)

<!-- Thank you for submitting this PR! :) -->

## Description

We're adding some tests that compare the output of metadata resolve.
Unfortunately, the results are nondeterministic because we use `HashMap`
/ `HashSet` in a lot of places. This replaces those uses with `BTreeMap`
and `BTreeSet` in `metadata-resolve`, and in a few places in `schema`
that rely on those types.

Some light reading around suggests that as well as giving us consistent
ordering, `BTree-` versions are better in terms of memory usage, esp
with < 1000 items (which I'm pretty sure most metadata items are)

https://www.reddit.com/r/rust/comments/xbkuc7/btreemap_vs_hashmap/
https://users.rust-lang.org/t/hashmap-vs-btreemap/13804/2
https://iq.opengenus.org/hashmap-and-btreemap-rust/

Functional no-op.

V3_GIT_ORIGIN_REV_ID: dbf49aefef0cd7084a3a37ef4fe9fc61257e1305
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c/server Related to server k/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cannot migrate from alpha20 to alpha21 with a restricted postgres user

4 participants