Updated Czech translation
gom: Clean up gom-resource.h
gom: Fix has_primary_key() return value

The has_primary_key() function was actually returning FALSE if the
resource had a primary set, the opposite of what we expected.
gom: Track whether GomResource objects come from the DB

We now track whether objects come from the database
(GomResourceGroup's fetch will tag items as such when getting them),
so that we can assert whether saves on that object would be an insert or
an update.

We also track the primary key changing back to zero/null, so that
something like getting an item from the DB, resetting the ID, and saving
it will create a duplicate as intended.

This fixes the failing test case introduced in
8e5602fa15fee310919a2ef087bc4726d4891f00
Added Slovenian translation
Added sl for Slovenian translation
Updated Slovenian translation
gom: Fix memory leak during migration

The object_types list's ownership is ours when we're called, so
make sure that we clear out the list when we're done with it.
gom: Fix fallout from object-types leak fix

The fix in 54737fd6c99fb20dc6c8877e035740b9a206258f was incomplete
and 2 test cases were crashing during migration.

Furthermore, the automatic migrator was freeing the list of object types
after migrating to version 1, making it crash for any migration past
that.
gom: API documentation improvements
0.2.0
gom: Add support for short and long integers

schar/uchar for guint8 and glong/gulong
gom: Better debug for gom_command_bind_param()
gom: Fix AND/OR filters memory handling

The values were getting double-freed. As gom_filter_get_values() returns
a new array, no need to stuff it inside another array that we would
create ourselves, just use that original array.

https://bugzilla.gnome.org/show_bug.cgi?id=731701
tests: GomFilter from 3 queries

https://bugzilla.gnome.org/show_bug.cgi?id=731701
Updated Spanish Translation
Added Greek translation
gom: Fix another memory management problem in GomFilter

Follow-up to 93694570fde8e29dff132644baa2efb18ef31ff5.

When appended to the target array, the values aren't refcounted, so
destroying the whole source array would destroy the values as well.
Disable the freeing of the individual items in the source array so
that they're not destroyed along with the source array. The destination
array will now assume ownership.
Added hu entry
Initial Hungarian translation