nil context should always default to context.Background

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Some API functions allow a nil context, but this is inconsistently documented.

      Others, like cursor.Close do not check for a nil context.

      To assist users who don't want to explicitly specify context.Background() on all calls, all calls that take a context should check for a nil argument and replace it with context.Background().

      All such functions should also have test coverage added for this case.

            Assignee:
            Benji Rewis (Inactive)
            Reporter:
            David Golden
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: