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

InvertedMap indices empty for multirow Table #6

Open
dag opened this issue Mar 11, 2013 · 6 comments
Open

InvertedMap indices empty for multirow Table #6

dag opened this issue Mar 11, 2013 · 6 comments
Assignees
Labels

Comments

@dag
Copy link
Collaborator

dag commented Mar 11, 2013

>>> :set +t
>>> fetch AffixK (state^?!wordData.ix "donri")
fromList ["do'i","dor"]
it :: Data.Set.Set Affix
>>> state^.wordData.withAll AffixK ["dor"]
fromList []
it :: Table WordData
>>> state^.wordData.withAny AffixK ["dor"]
fromList []
it :: Table WordData
@dag
Copy link
Collaborator Author

dag commented Mar 11, 2013

If @Taneb could take a looksie that'd be great!

@ghost ghost assigned Taneb Mar 11, 2013
@dag
Copy link
Collaborator Author

dag commented Mar 16, 2013

The t -> [a] instance seems to work though:

>>> state^..wordData.withAny (toListOf folded . fetch AffixK) ["dor"].folded.word'
["donri"]

@dag
Copy link
Collaborator Author

dag commented Mar 16, 2013

Although I'm not sure about withAll for that instance:

>>> state^.wordData.withAll (toListOf folded . fetch AffixK) ["dor"] & count
5911

Shoudn't withAll and withAny be equivalent when given a singleton list?

@ekmett
Copy link
Owner

ekmett commented Apr 12, 2013

They should be, yes.

@dag
Copy link
Collaborator Author

dag commented Aug 5, 2013

It looks like the inverted indices are correctly set up for singleton tables, but they're empty for tables with more than one row. It also seems that withAny and withAll work correctly for singleton tables. This suggests to me that the problem likely is in either unsafeInsert or deleteCollisions (or both).

@ghost
Copy link

ghost commented Dec 4, 2016

I'd like to investigate this issue but there is not enough context given in the report to reproduce the result myself. I know it's been quite a while since this issue was opened but if the reporter still has the code that produced this issue would they mind posting a more complete test case?

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

No branches or pull requests

3 participants