Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: SAP/python-pyodata
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: SAP/python-pyodata
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: experimental_v3
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 4 files changed
  • 1 contributor

Commits on Feb 24, 2020

  1. model: implement floating point numbers handling

    It turned out that PyOData does not understand floating point numbers as
    defined in OData standards.
    
    This commit adds special formatters and parsers for floating point
    numbers as represented in OData standards.
    
    The commit also adds the type Edm.Float which is not defined in
    the OData V2 standard but it is most probably of a new created
    Edm format specification.
    
    The OData standard is kinda fuzzy and even examples do not match
    the requirements. Hence, do not be confused by the fact that we do not
    add the suffixes {d,f} to string representations and we don't check if
    converted literals have the suffix.
    
    Closes #81
    filak-sap committed Feb 24, 2020
    Configuration menu
    Copy the full SHA
    c05074b View commit details
    Browse the repository at this point in the history

Commits on Mar 2, 2020

  1. Configuration menu
    Copy the full SHA
    5ceafac View commit details
    Browse the repository at this point in the history

Commits on Mar 5, 2020

  1. model: drop the 7th microseconds digit

    Edm.DateTime allows 7 digits for microseconds.
    Python allows 6 digits for microseconds.
    
    I think we can ignore those hundreds of nanoseconds
    without the need for rounding - i.e. we can simply
    ignore this information.
    
    https://blogs.sap.com/2017/01/05/date-and-time-in-sap-gateway-foundation/comment-page-1/#comment-497276
    filak-sap committed Mar 5, 2020
    Configuration menu
    Copy the full SHA
    726d949 View commit details
    Browse the repository at this point in the history
  2. service: do not read response.d if not exists

    Eh, that's a stupid approach but I have no time to think.
    filak-sap committed Mar 5, 2020
    Configuration menu
    Copy the full SHA
    a545948 View commit details
    Browse the repository at this point in the history
Loading