nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-19 22:35:50 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove 'considerations' and 'index efficiency'

Browse Source
This commit is contained in:
dskvr 2024-08-29 16:55:30 +02:00
parent 3086a205be
commit b0491854f8
1 changed files with 1 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
119.md
View File

@ -22,17 +22,4 @@ filters: {
- `AND` **MUST** take precedence over `OR`
- Tags used in `AND` **SHOULD NOT** be used in standard `OR` tags [`#`]
- Any tag used in `AND` **SHOULD** be ignored in `OR`
## Considerations
- New field for `NIP-11.limitations`: `max_tags_per_and` and `max_tags_and`
- Benchmarking should be conducted to validate that bandwidth and protocol usability as benefits supercede implementation and clock-time cost.
## Index Efficiency
| Index Type | AND Operation Efficiency | OR Operation Efficiency | Notes |
|----------------|--------------------------|-------------------------|-------|
| B-Tree | High | Moderate | B-Tree indexes are very efficient for AND operations, especially with compound indexes. For OR operations, they are less efficient than for AND, as the database engine might need to traverse multiple paths. |
| Bitmap | High | High | Bitmap indexes excel in both AND and OR operations, particularly for columns with low cardinality. They utilize fast bitwise operations, making them ideal for read-heavy environments. |
| Hash | Not Applicable | Not Applicable | Hash indexes are designed for equality checks and do not directly support range-based queries or optimize for AND/OR operations efficiently. |
| Full-Text | High | High | Optimized for text search, full-text indexes efficiently handle both AND and OR conditions, making them suitable for complex text queries. |
- Any tag used in `AND` **SHOULD** be ignored in `OR`