1. 11 May, 2021 1 commit
  2. 10 Feb, 2021 2 commits
  3. 18 Feb, 2020 11 commits
  4. 17 Feb, 2020 4 commits
    • Bastien Nocera's avatar
      0.4 · 26816b74
      Bastien Nocera authored
    • Bastien Nocera's avatar
      tests: Greatly reduce the size of the stress test · 3ae8528b
      Bastien Nocera authored
      Closes: #22
    • Bastien Nocera's avatar
      build: Fix meson warning · 95789bfd
      Bastien Nocera authored
      DEPRECATION: Project targeting '>= 0.38.1' but tried to use feature deprecated since '0.48.0': python3 module
      WARNING: Deprecated features used:
       * 0.48.0: {'python3 module'}
    • Bastien Nocera's avatar
      gom: Fix primary-key not being monitored · 61f919a0
      Bastien Nocera authored
      The GomResourceClass associated with an child class (such as
      ItemResourceClass in much of our tests) isn't the same as the one in
      GomResourceClass' class_init().
      We have the right GomResourceClass subclass during
      gom_resource_init(), but GType has temporarily changed its g_class
      pointer to point to the GomResourceClass instance for GOM_TYPE_RESOURCE
      while calling gom_resource_init().
      It will later change the g_class pointer back to the GomResourceClass
      instance for ITEM_TYPE_RESOURCE (as is used in most of our tests).
      g_class is used by G_OBJECT_GET_CLASS() to get the class struct instance.
      See https://gitlab.gnome.org/GNOME/glib/blob/341c58b44a698c68ba96639636fd02e54cbaddd7/gobject/gtype.c#L1860
      Add a constructed vfunc so that we can get the GomResourceClass
      associated with the child class' instance after the g_class swap, with,
      this time, the primary_key correctly set to a non-empty value.
      This empty value was also causing warnings (and fatal warnings in test
      suites) with newer versions of GLib as it tried to connect to the
      "notify::" signal.
      See glib@5e89ba5a
      Closes: #24
  5. 11 Feb, 2020 1 commit
  6. 18 Jul, 2019 2 commits
    • Bob Ham's avatar
      tests: Add datetime test to check sanity of datetime columns · 320df01c
      Bob Ham authored
      In particular, check that NULL values are stored in the database as
    • Bob Ham's avatar
      gom: Store NULL GDateTimes in the database as NULL · e80ff491
      Bob Ham authored
      Currently Gom will store NULL GDateTimes in the database as a string
      representing the epoch, '1970-01-01T00:00:00Z', instead of NULL.  This
      unneccessarily increases the storage requirements of every NULL
      GDateTime column in every row by 20 bytes.  This also presents a loss
      of information: there's no way to distinguish between the valid input
      values of the epoch and NULL.  The API user has to account for the way
      in which the library is transforming data values.
      To fix this, we store NULL GDateTime values in the database as NULL
  7. 17 Jul, 2019 1 commit
  8. 27 Feb, 2019 3 commits
  9. 16 Dec, 2018 2 commits
  10. 25 Jul, 2018 2 commits
  11. 09 Aug, 2017 4 commits
  12. 21 Jun, 2017 2 commits
  13. 16 May, 2017 1 commit
  14. 29 Apr, 2017 4 commits