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.

Sign up for GitHub

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

Jump to bottom

Merging of attributes of the same value but different types #34

Open
trungdong opened this issue Apr 24, 2014 · 1 comment
Open

Merging of attributes of the same value but different types #34

trungdong opened this issue Apr 24, 2014 · 1 comment
Labels
bug prov.model

Comments

@trungdong
Copy link
Owner

The (extra) attribute-value pairs of a record have set-like behaviour, i.e. entity(ex:a, [ex:v=2, ex:v=2]) is considered equivalent to entity(ex:a, [ex:v=2]). Therefore, attribute-value pairs are stored in a set by prov.model.

However, when adding values to a set, Python considers 2 (int) and 2.0 (float) the same, resulting only one values retained in the set.
trungdong added a commit that referenced this issue Apr 24, 2014
@trungdong
prov.model: Temporary disabled auto-mapping xsd:double and xsd:long l…
9a83973 
…iterals to Python's float and long values to avoid the bug #34
trungdong added a commit that referenced this issue Apr 24, 2014
@trungdong
Revert "prov.model: Temporary disabled auto-mapping xsd:double and xs…
6e0dd93 
…d:long literals to Python's float and long values to avoid the bug #34"

This reverts commit 9a83973.
@satra
Copy link
Contributor

satra commented Oct 12, 2016

this is also true of set((1, True)),

@satra satra mentioned this issue Oct 13, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug prov.model
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@satra @trungdong