Bug 1025106
Summary: | [XMLRPC][Serialization] Improve model's serialization | ||
---|---|---|---|
Product: | [Other] TCMS | Reporter: | cqi |
Component: | XMLRPC | Assignee: | Yang Ren <ryang> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | Devel | CC: | ryang |
Target Milestone: | --- | Keywords: | Improvement |
Target Release: | 3.8.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
cqi
2013-10-31 03:01:00 UTC
Yeah, this sounds doable. So, instead of getting each field value by traversing all the fields of a model, a better way would be to calculate a list of Django LookUp field names and give it to the .values() method. Okay, I'd like to see the how much of a difference it makes for an existing XMLRPC API. Also, I don't suspect this introduces inconsistency into XMLRPC APIs right? (In reply to Chaobin Tang from comment #1) > Yeah, this sounds doable. > > So, instead of getting each field value by traversing all the fields of a > model, a better way would be to calculate a list of Django LookUp field > names and give it to the .values() method. > > Okay, I'd like to see the how much of a difference it makes for an existing > XMLRPC API. > > Also, I don't suspect this introduces inconsistency into XMLRPC APIs right? Yes. Rewrite must ensure the original behavior not changed. Cache mechanism could be introduced to cache each model's fields' names. Because, they are immutable during the runtime once TCMS begins to run. |