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

JugglingDB doesnt creates incorrect Index when value field is defined as a string false #7

Open
agurha opened this issue Jun 5, 2013 · 0 comments

Comments

@agurha
Copy link

agurha commented Jun 5, 2013

So when we have a see like below

Content.seed ->
id: 2
type: 'statusupdate'
imported: undefined
title: 'Text!!!'
text: '

Hello World

'
excerpt: undefined
previewImage: undefined
attachment: undefined
poll: undefined
location: ''
comments: []
commentsTotal: undefined
repliesTotal: undefined
likes: []
dislikes: []
flags: []
hasFlag: false
likesTotal: 0
views: undefined
score: 0
groupId: 1
replyToId: undefined
tagString: ''
authorId: 1
privacy: undefined
createdAt: 'Tue Apr 02 2013 18:33:51'
updatedAt: 'Mon May 13 2013 19:37:12'
timestamp: 1364913231331
timeSince: 'a month ago'
priority: undefined
url: undefined
fulltext: 'Text!!!

Hello World.

[]'
importData: undefined
tags: []
tagNames: ''
thumbnailPreview: null
tweetText: undefined
facebookText: undefined
pinTime: 0
adjustedDate: 'Tue Apr 02 2013 18:33:51'
size: 1
stage: 'false'
stagePosition: 0

Here we are defining value as string 'false' for 'stage' key . In this case Index created in Redis is

"z:test/Content:stage:true"

when expected value would be "z:test/Content:stage:false"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant