Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: genesis and current locations using materialized view #138

Merged
merged 2 commits into from
Jul 9, 2023

Conversation

rafaelcr
Copy link
Collaborator

@rafaelcr rafaelcr commented Jul 9, 2023

No description provided.

@rafaelcr rafaelcr temporarily deployed to Preview July 9, 2023 16:38 — with GitHub Actions Inactive
@github-actions
Copy link

github-actions bot commented Jul 9, 2023

Vercel deployment URL: https://ordinals-itzc2r2z8-blockstack.vercel.app 🚀

@rafaelcr rafaelcr temporarily deployed to Preview July 9, 2023 16:44 — with GitHub Actions Inactive
@rafaelcr rafaelcr merged commit 88edee4 into master Jul 9, 2023
@rafaelcr rafaelcr deleted the fix/sat-table branch July 9, 2023 16:50
blockstack-devops pushed a commit that referenced this pull request Jul 9, 2023
## [0.4.11](v0.4.10...v0.4.11) (2023-07-09)

### Bug Fixes

* genesis and current locations using materialized view ([#138](#138)) ([88edee4](88edee4))
@blockstack-devops
Copy link

🎉 This PR is included in version 0.4.11 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

blockstack-devops pushed a commit that referenced this pull request Jul 12, 2023
## [1.0.0-beta.3](v1.0.0-beta.2...v1.0.0-beta.3) (2023-07-12)

### Bug Fixes

* allow multiple transfers per inscription per block ([#131](#131)) ([9fee5ac](9fee5ac))
* genesis and current locations using materialized view ([#138](#138)) ([88edee4](88edee4))
* ignore json content for current build ([#140](#140)) ([909f79f](909f79f))
* mark intractable `/inscriptions` result counts as 0 to avoid DB bottlenecks ([#142](#142)) ([2d1fa8f](2d1fa8f))
* move to many-to-many genesis and current table ([#139](#139)) ([2b6b6ec](2b6b6ec))
* patch ordinal number for transfers replay ([#134](#134)) ([8d3fb5b](8d3fb5b))
* rename location pointer tables ([b84d27e](b84d27e))
* skip normalization for now ([#136](#136)) ([85de25f](85de25f))
@blockstack-devops
Copy link

🎉 This PR is included in version 1.0.0-beta.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

g0drlc added a commit to g0drlc/btc-ordinals-api that referenced this pull request Jul 14, 2024
## [0.4.11](hirosystems/ordinals-api@v0.4.10...v0.4.11) (2023-07-09)

### Bug Fixes

* genesis and current locations using materialized view ([#138](hirosystems/ordinals-api#138)) ([88edee4](hirosystems/ordinals-api@88edee4))
g0drlc added a commit to g0drlc/btc-ordinals-api that referenced this pull request Jul 14, 2024
## [1.0.0-beta.3](hirosystems/ordinals-api@v1.0.0-beta.2...v1.0.0-beta.3) (2023-07-12)

### Bug Fixes

* allow multiple transfers per inscription per block ([#131](hirosystems/ordinals-api#131)) ([9fee5ac](hirosystems/ordinals-api@9fee5ac))
* genesis and current locations using materialized view ([#138](hirosystems/ordinals-api#138)) ([88edee4](hirosystems/ordinals-api@88edee4))
* ignore json content for current build ([#140](hirosystems/ordinals-api#140)) ([909f79f](hirosystems/ordinals-api@909f79f))
* mark intractable `/inscriptions` result counts as 0 to avoid DB bottlenecks ([#142](hirosystems/ordinals-api#142)) ([2d1fa8f](hirosystems/ordinals-api@2d1fa8f))
* move to many-to-many genesis and current table ([#139](hirosystems/ordinals-api#139)) ([2b6b6ec](hirosystems/ordinals-api@2b6b6ec))
* patch ordinal number for transfers replay ([#134](hirosystems/ordinals-api#134)) ([8d3fb5b](hirosystems/ordinals-api@8d3fb5b))
* rename location pointer tables ([b84d27e](hirosystems/ordinals-api@b84d27e))
* skip normalization for now ([#136](hirosystems/ordinals-api#136)) ([85de25f](hirosystems/ordinals-api@85de25f))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants