1. 28 Jul, 2019 2 commits
  2. 27 Jul, 2019 3 commits
  3. 14 May, 2019 1 commit
  4. 15 Feb, 2019 1 commit
  5. 08 Feb, 2019 1 commit
  6. 01 Feb, 2019 1 commit
  7. 02 Jan, 2019 8 commits
  8. 17 Dec, 2018 1 commit
    • Steven Buss's avatar
      Add support for stable Func keys in App Engine second gen (#184) · e9657d88
      Steven Buss authored
      Func keys include the filename where the Func is created. The filename is parsed according to these rules:
      
      * Paths in package main are shortened to just the file name (github.com/foo/foo.go -> foo.go)
      * Paths are stripped to just package paths (/go/src/github.com/foo/bar.go -> github.com/foo/bar.go)
      * Module versions are stripped (/go/pkg/mod/github.com/foo/bar@v0.0.0-20181026220418-f595d03440dc/baz.go -> github.com/foo/bar/baz.go)
      e9657d88
  9. 03 Dec, 2018 2 commits
  10. 31 Oct, 2018 1 commit
  11. 29 Oct, 2018 2 commits
    • Steven Buss's avatar
      Drop pre 18 (#165) · 80663353
      Steven Buss authored
      Drop support for Go < 1.9
      80663353
    • Michael Traver's avatar
      Add functions that check which environment the app is running in (#170) · b2f5f02a
      Michael Traver authored
      This is motivated by the fact that second-generation runtimes
      (>= Go 1.11) do not set the appengine build tag, so the build tag alone
      is not sufficient to determine whether an app is running in the standard
      environment. We can check for a second-gen runtime with $GAE_ENV.
      The new functions centralize this logic so other packages don't have to
      worry about the build tags and env vars.
      
      Added:
      - IsStandard reports whether the App Engine app is running in the
        standard environment. This includes both the first generation
        runtimes (<= Go 1.9) and the second generation runtimes (>= Go 1.11).
      - IsFlex reports whether the App Engine app is running in the flexible
        environment.
      - IsAppEngine reports whether the App Engine app is running on App
        Engine, in either the standard or flexible environment.
      
      Test: Deployed an app to go1/go1.8, go1/go1.9, go111, and flex. The app
            prints out the return val of each of the new functions. Verified
            correctness.
      b2f5f02a
  12. 18 Sep, 2018 2 commits
  13. 27 Aug, 2018 1 commit
  14. 31 Jul, 2018 1 commit
  15. 30 Jul, 2018 1 commit
  16. 26 Jun, 2018 5 commits
  17. 21 May, 2018 1 commit
  18. 16 May, 2018 1 commit
    • JINNOUCHI Yasushi's avatar
      datastore: enable to set query batch size (#90) · b9aad5d6
      JINNOUCHI Yasushi authored
      * datastore: enable to set query batch size
      
      This adds q.BatchSize() method to avoid the error that claims too many
      datastore.next() calls due to the lack of specifying the `count`
      property (= batch size).
      
      Fixes #88
      
      * Disallow negative values for BatchSize
      
      * Deal with negative value for t.limit
      
      and clean up to be more readable
      
      * Add comment about possible values for t.count
      
      * Use the same `if` block as in `Run()` for `count`
      
      * Make BatchSize restrict to be greater than zero
      b9aad5d6
  19. 27 Apr, 2018 1 commit
  20. 17 Apr, 2018 1 commit
  21. 05 Apr, 2018 1 commit
    • Michael Traver's avatar
      datastore: add AllocateIDRange (#130) · 0a24098c
      Michael Traver authored
      Allows a range of IDs to be allocated, as is possible with the Python
      and Java appengine APIs. Note that because of the way the datastore
      backend is implemented, a request to allocate ID range [x, y] is
      actually a request to allocate range [1, y]. This is consistent with
      the behavior in Python and Java.
      
      Test: Because we don't have a mock datastore, no tests are added to
            key_test.go (AllocateIDs is also not covered in key_test.go).
            Instead, I made test apps in Go (using these changes) and Python
            (using stock google.appengine.ext.db) and exercised each API's
            ID range allocation implementation with the dev_appserver.py
            datastore and the prod datastore. The Go implementation matches
            Python's behavior.
      
      Fixes #97
      0a24098c
  22. 03 Apr, 2018 1 commit
  23. 29 Mar, 2018 1 commit