-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Find key createReadStream #778
Comments
Duplicate of Level/level#203. |
Why you not answering me & closing issue? if their any problem please discuss with me clearly. |
I or someone else will answer when we have time and if we feel like it. Level is an open source project run by volunteers. Personally I hesitated to answer because I don't want to just write your application for you, without teaching why it works the way it does. An understanding of lexicographic order is essential for unlocking the power of level and I was unsure how to approach this, not knowing your background, or what documentation and prior art you looked at before opening a ticket. We lack a "getting started" guide on this topic, otherwise I would refer to that, but plenty of examples do exist. I closed this because it's an exact duplicate of Level/level#203. I stated that clearly. Please be aware that opening duplicate tickets or repeatedly asking for an answer will be perceived as spam and decrease the chance that you'll get an answer. |
@vweevers I understand your words, Sorry for making duplicate issue. |
Not able to find specific part of the key "uid3" using createReadStream
const level = require('level')
const db = level('my-db')
setImmediate(async () => {
await db.put('type:user:uid1', 'value')
await db.put('type:user:uid2', 'value')
await db.put('type:user:uid3', 'value')
// not working-
db.createReadStream({ gte: '\xff:uid3' }).on('data', function (data) {
console.log(data.key, '=', data.value)
})
// not working-
db.createReadStream({ gte: 'uid3' }).on('data', function (data) {
console.log(data.key, '=', data.value)
})
});
The text was updated successfully, but these errors were encountered: