Remove non-cursor support from dbiDel(), dbiPut() and dbiGet()
authorPanu Matilainen <pmatilai@redhat.com>
Wed, 20 Apr 2011 10:18:54 +0000 (13:18 +0300)
committerPanu Matilainen <pmatilai@redhat.com>
Wed, 20 Apr 2011 10:18:54 +0000 (13:18 +0300)
commit0f112aa9f9e13153703b43de935c7bb3c57b4a45
tree4a1f8c7a06f87acd95556bf7ef630e54225f672c
parentbe40e1fb9227a76a7086f4a7d707a750f3107eee
Remove non-cursor support from dbiDel(), dbiPut() and dbiGet()
- Previously these functions would silently fall back to non-cursor
  access when (accidentally) called with NULL cursor. This can lead
  to different results for cases where cursor is actually required,
  without any indication of it being an error. Make them fail
  with EINVAL for NULL cursors so it gets trapped in rpmdb.c uses.
lib/backend/db3.c