Skip to content

Conversation

@mtalexan
Copy link
Owner

Allows completely new V1 requests within the same application by creating new V1Meta objects.

kbielefe and others added 16 commits March 27, 2014 17:29
…allow applications to clear the cache by creating a new v1meta object, without having to restart their application.
VersionOne API supports utf-8, but generate_update_doc method could not handle unicode object correctly.
For example, if I'd like to update asset with Japanese words, generate_update_doc method raises UnicodeEncodeError.
This commit fixed that issue to use decode method instead of str.
History attribute now returns correct versions of the core object.
v1meta: Fix UnicodeEncodeError when using utf-8 in newvalue
Cleaned up the V1Query class to use Python-standard data member naming conventions for private members.
Added support for using len() on the query, and a length(), both of which optimally run the base query.
Standardized the sel_string and select() usage so they can both be used instead of sel_string making select() fail to function.
Update the README
…h() to support determining total possible items when paging
Support Python3, fix indent, add feature support, cleanup setup.py
@mtalexan mtalexan force-pushed the master branch 2 times, most recently from 7459a2f to c1f947e Compare June 21, 2018 18:06
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

Successfully merging this pull request may close these issues.

7 participants