fix: mark intractable /inscriptions result counts as 0 to avoid DB bottlenecks
#142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Vercel deployment URL: https://ordinals-awhqpv9en-blockstack.vercel.app 🚀 |
blockstack-devops
pushed a commit
that referenced
this pull request
Jul 11, 2023
## [0.4.14](v0.4.13...v0.4.14) (2023-07-11) ### Bug Fixes * mark intractable `/inscriptions` result counts as 0 to avoid DB bottlenecks ([#142](#142)) ([2d1fa8f](2d1fa8f))
|
🎉 This PR is included in version 0.4.14 🎉 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))
|
🎉 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.14](hirosystems/ordinals-api@v0.4.13...v0.4.14) (2023-07-11) ### Bug Fixes * mark intractable `/inscriptions` result counts as 0 to avoid DB bottlenecks ([#142](hirosystems/ordinals-api#142)) ([2d1fa8f](hirosystems/ordinals-api@2d1fa8f))
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will buy us time to look for a real solution (combination of materialized views, etc.)