gem-hunter
主要言語: Groovy
Grails plugin to use postgresql native elements such as arrays, hstores,...
This is a Grails plugin that provides Hibernate user types to use PostgreSQL native types such as Array, Hstore, Json, Jsonb, ..., from a Grails application. It also provides new criteria to query these new native types.
Currently, the plugin supports array, hstore, json and jsonb fields as well as some query methods. More native types and query methods will be added in the future.
The Grails 8 version of this plugin supports both Hibernate 5 and Hibernate 7, with a plugin for each.
In build.gradle add the dependencies for the Hibernate version of your application.
Hibernate 5:
dependencies {
//...
implementation 'io.github.gpc:grails-postgresql-extensions:<version>'
implementation 'org.apache.grails:grails-data-hibernate5'
//...
}Hibernate 7:
dependencies {
//...
implementation 'io.github.gpc:grails-postgresql-extensions-hibernate7:<version>'
implementation 'org.apache.grails:grails-data-hibernate7'
//...
}Both plugins provide the same user types, dialect, criteria and orders, in the same packages, so the domain classes and queries of an application do not change when it moves from Hibernate 5 to Hibernate 7.
Note
With GORM 8.0.0 for Hibernate 7, the default native id generator does not create its sequences on PostgreSQL
(apache/grails-core#16561).
Until this is fixed in GORM, use the sequence generator in grails-app/conf/application.groovy:
grails.gorm.default.mapping = { id generator: 'sequence' }
HstoreHelper and PgArrayUtils, moved to the
grails-postgresql-extensions-core module, which both plugins depend on. Their packages did not change.PgArrayUtils.getValueAsArrayOfType now throws an IllegalArgumentException instead of a HibernateException for
values of an unsupported type. The array criteria still throw a HibernateException.GORM 8.0.0 for Hibernate 7 has no API for custom criteria to use the joins of the query, or to order by an SQL formula (apache/grails-core#16563), so the plugin works around it:
createAlias uses the same join as the GORM criteria on the alias, when the
alias uses an inner join. GORM 8.0.0 creates the join of an alias as an inner join even when createAlias asks for an
outer join (apache/grails-core#16562), so for an outer join alias the criteria of the plugin use an
outer join, but GORM criteria on the same alias do not.order(sqlFormula(...)) and order(byRandom()) are added to the orders when the query is created, in the position
they were called in. Calling them inside or {} or not {} does not change the result of the junction.
An or {} that only contains such an order is empty, which matches no rows.After installing the plugin you have to use a new PostgreSQL Hibernate Dialect in your application. Add it to the
grails-app/conf/application.yml file:
--- dataSource: pooled: true jmxExport: true driverClassName: org.postgresql.Driver username: user password: password url: jdbc:postgresql://localhost:5432/db_name dbCreate: update hibernate: dialect: gpc.pgext.hibernate.PostgresqlExtensionsDialect
If you just add the dialect, hibernate will create a new sequence for every table to generate the sequential ids used for the primary keys instead of a global sequence for all your tables.
You can also deactivate this behavior and create only one unique sequence for all the tables with the following property in your datasource definition:
Add the following to grails-app/conf/application.groovy:
grails.gorm.default.mapping = { id generator: 'org.hibernate.id.enhanced.SequenceStyleGenerator', params: [prefer_sequence_per_entity: true] }
Please be aware that Hibernate 5 has changed the default name of the sequences so for a domain class TestMapJson the
table name is test_map_json and the sequence name is seq_test_map_json in Hibernate 4 and testmapjson_seq in
Hibernate 5.
The plugin supports the definition of Integer, Long, Float, Double, String, and Enum arrays in your domain
classes.
The Enum arrays behaves almost identical to Integer arrays in that they store and retrieve an array of ints. The
difference, however, is that this is used with an Array of Enums, rather than ints. The Enums are serialized to their
ordinal value before persisted to the database. On retrieval, they are then converted back into their original Enum
type.
import gpc.pgext.hibernate.usertype.ArrayType class Like { Integer[] favoriteNumbers = [] Long[] favoriteLongNumbers = [] Float[] favoriteFloatNumbers = [] Double[] favoriteDoubleNumbers = [] String[] favoriteMovies = [] Juice[] favoriteJuices = [] UUID[] favoriteMovieUUIDs = [] static enum Juice { ORANGE(0), APPLE(1), GRAPE(2) private final int value Juice(int value) { this.value = value } } static mapping = { favoriteNumbers type:ArrayType, params: [type: Integer] favoriteLongNumbers type:ArrayType, params: [type: Long] favoriteFloatNumbers type:ArrayType, params: [type: Float] favoriteDoubleNumbers type:ArrayType, params: [type: Double] favoriteMovies type:ArrayType, params: [type: String] favoriteJuices type:ArrayType, params: [type: Juice] favoriteMovieUUIDs type:ArrayType, params: [type: UUID] } }
Now you can create domain objects using lists (or arrays) of integers, longs and strings and when you save the object it will be stored as an postgresql array:
def myLikes = new Like(favoriteNumbers: [5, 17, 9, 6], favoriteLongNumbers: [123, 239, 3498239, 2344235], favoriteFloatNumbers: [0.3f, 0.1f], favoriteDoubleNumbers: [100.33d, 44.11d], favoriteMovies: ["Spiderman", "Blade Runner", "Starwars"], favoriteJuices: [Like.Juice.ORANGE, Like.Juice.GRAPE]) myLikes.save()
And now, with psql:
=# select * from like;
id | favorite_long_numbers | favorite_float_numbers | favorite_double_numbers | favorite_movies | favorite_numbers | favorite_juices
----+---------------------------+---------------------------+---------------------------+----------------------------------------+------------------+----------------
1 | {123,239,3498239,2344235} | {0.3,0.1} | {100.33,44.11} | {Spiderman,"Blade Runner",Starwars} | {5,17,9,6} | {0,2}
The plugin also includes some Hibernate criteria to use in your queries. Please check the services and the tests created to see all usage examples.
You can also check the official Postgresql Array operators.
With this criteria you can get all the rows that contain all the values in the array field. To use it just use the new
criteria pgArrayContains:
// number can be just a value... def number = 3 def result = Like.withCriteria { pgArrayContains 'favoriteNumbers', number } // ...or a list def numbers = [5, 17] def result = Like.withCriteria { pgArrayContains 'favoriteNumbers', numbers } // If using enums, pass the enum right through def juices = Like.Juice.ORANGE def result = Like.withCriteria { pgArrayContains 'favoriteJuices', juices }
With this criteria you can get all the rows that are contained by the values. To use it just use the new criteria
pgArrayIsContainedBy:
// movie can be just a string or a list def movie = "Starwars" // or movie = ["Starwars"] def result = Like.withCriteria { pgArrayIsContainedBy 'favoriteMovies', movie } // The plugin also support joins def movies = ["Starwars", "Matrix"] def results = User.withCriteria { like { pgArrayIsContainedBy 'favoriteMovies', movies } }
With this criteria you can get all the rows that contains any of the values. To use it just use the new criteria
pgArrayOverlaps:
def result = Like.withCriteria { pgArrayOverlaps 'favoriteNumbers', numbers }
With this criteria you can get all the rows that contains an-empty array in the selected field. To use it just use the
new criteria pgArrayIsEmpty:
def result = Like.withCriteria { pgArrayIsEmpty 'favoriteMovies' }
With this criteria you can get all the rows that contains a not empty array in the selected field. To use it just use
the new criteria pgArrayIsNotEmpty:
def result = Like.withCriteria { pgArrayIsNotEmpty 'favoriteMovies' }
This criteria is a mix of the pgContains and pgIsEmpty. Sometimes you have to execute 'pgContains' criteria if the
list has elements or a 'pgIsEmpty' if the list is empty. It could be something like this:
def numbers = ... // A list with zero or more elements def result = Like.withCriteria { if (numbers) { pgArrayContains 'favoriteNumbers', numbers } else { pgArrayIsEmpty 'favoriteMovies' } }
With pgIsEmptyOrContains you can write the previous code as follows:
def numbers = ... // A list with zero or more elements def result = Like.withCriteria { pgArrayIsEmptyOrContains 'favoriteNumbers', numbers }
With this criteria you can get all the rows that are equal to a value. To use it just use the new criteria pgArrayEquals:
def result = Like.withCriteria { pgArrayEquals 'favoriteNumbers', numbers }
With this criteria you can get all the rows that are not equal to a value. To use it just use the new criteria
pgArrayNotEquals:
def result = Like.withCriteria { pgArrayNotEquals 'favoriteNumbers', numbers }
With this criteria you can get all the rows that are ilike to a value. To use it just use the new criteria pgArrayILike.
It only can be used on arrays of string.
It uses the ilike syntaxis, so you can do for example:
def result = Like.withCriteria { pgArrayILike 'favoriteMovies', "%tarwar%" }
The first thing you need to do is install hstore support in Postgresql. In Debian/Ubuntu you have to install the
postgresql-contrib package:
sudo apt-get install postgresql-contrib-9.4
Once the package is installed in the system you have to create the extension in the database you want to use hstore into:
CREATE EXTENSION hstore;
You can test that the hstore extension is correctly installed running:
=# SELECT 'foo=>bar, xxx=>yyy'::hstore;
hstore
----------------------------
"foo"=>"bar", "xxx"=>"yyy"
(1 row)
You only have to define the domain class with a Map attribute and use the Hibernate user type HstoreMapType.
import net.kaleidos.hibernate.usertype.HstoreMapType class TestHstore { Map testAttributes String anotherProperty static mapping = { testAttributes type: HstoreMapType } }
Now you can create and instance of the domain class. Due to a limitation of the Hstore Postgresql type you can only store Strings as key and value.
def instance = new TestHstore(testAttributes: [foo: "bar"], anotherProperty: "Groovy Rocks!") instance.save() def instance2 = new TestHstore(testAttributes: [xxx: 1, zzz: 123], anotherProperty: "") instance2.save()
=# select * from test_hstore;
id | version | another_property | test_attributes
----+---------+------------------+-----------------
1 | 0 | Groovy Rocks! | "foo"=>"bar"
2 | 0 | | "xxx"=>"1", "zzz"=>"123"
The following criteria operations are available to query rows using the Hstore custom type. You can check the services and the tests created to see all usage examples.
You can also check the official Postgresql Hstore operators.
With this operation you can search for rows that contain an Hstore with the key passed as parameter.
def wantedKey = "my-custom-key" def result = MyDomain.withCriteria { pgHstoreContainsKey "attributes", wantedKey }
You can search for data that contains certain pairs of key and value.
def result = Users.withCriteria { pgHstoreContains 'configuration', ["language": "es"] }
The operation is contained can be used when looking for rows that has all the elements in the map passed as parameter.
def result = TestHstore.withCriteria { pgHstoreIsContained 'testAttributes', ["1": "a", "2": "b"] }
The example above returns the rows that contains elements like:
testAttributes = ["1": "a"]
testAttributes = ["2": "b"]
testAttributes = ["1": "a", "2": "b"]
This criteria can also be used to look for exact matches.
With this operation you can search for rows that contain an Hstore in which any value matches (ilike) to the parameter. It uses the ilike syntaxis, so you can do for example:
def wantedValue = "%my-value%" def result = MyDomain.withCriteria { pgHstoreILikeValue "attributes", wantedKey }
To define a json field you only have to define a Map field and use the JsonMapType hibernate user type.
import net.kaleidos.hibernate.usertype.JsonMapType class TestMapJson { Map data static constraints = { } static mapping = { data type: JsonMapType } }
Now you can create and instance of the domain class:
def instance = new TestMapJson(data: [name: "Iván", age: 35, hasChilds: true, childs: [[name: 'Judith', age: 8], [name: 'Adriana', age: 5]]]) instance.save()
=# select * from test_map_json;
id | version | data
----+---------+-------------------------------------------------------------------------------------------------------------
1 | 0 | {"hasChilds":true,"age":35,"name":"Iván","childs":[{"name":"Judith","age":8},{"name":"Adriana","age":5}]}
As you can see the plugin converts to Json automatically the attributes and the lists in the map type.
The plugin provides some criterias to query json fields. You can check the official Postgresql Json functions and operators in case you need additional ones.
With this criteria you can check if a json field contains some value in some key. To use it just use the criteria
pgJsonHasFieldValue:
def obj1 = new TestMapJson(data: [name: 'Iván', lastName: 'López']).save(flush: true) def obj2 = new TestMapJson(data: [name: 'Alonso', lastName: 'Torres']).save(flush: true) def obj3 = new TestMapJson(data: [name: 'Iván', lastName: 'Pérez']).save(flush: true) def result = TestMapJson.withCriteria { pgJsonHasFieldValue 'data', 'name', 'Iván' }
The previous criteria will return all the rows that have a name attribute in the json field data with the value
Iván. In this example obj1 and obj3.
With this criterion you can use more operators using a syntax close to the one described in Postgresql documentation.
To use it just use pgJson:
def obj1 = new TestMapJson(data: [name: 'Iván', lastName: 'López', other: [followersCount: 150]]).save(flush: true) def obj2 = new TestMapJson(data: [name: 'Alonso', lastName: 'Torres', other: [followersCount: 148]]).save(flush: true) def obj3 = new TestMapJson(data: [name: 'Iván', lastName: 'Pérez', other: [followersCount: 149]]).save(flush: true) def result1 = TestMapJson.withCriteria { pgJson 'data', '->>', 'name', 'ilike', '%iv%' }
The previous query will return all the rows that have a name attribute in the json field data containing iv
(case insensitive). In this example obj1 and obj3.
def result2 = TestMapJson.withCriteria { pgJson 'data', '#>>', '{other, followersCount}', '>', 149 }
The previous query will return all the rows that have an other value whose followersCount value is greater than
149. In this example obj1.
Since postgresql-extensions version 4.4.0 it is possible to use Postgresql Jsonb instead of just json. You need to use at least Postgresql 9.4.
To define a jsonb field you only have to define a Map field and use the JsonbMapType hibernate user type.
import net.kaleidos.hibernate.usertype.JsonbMapType class TestMapJsonb { Map data static constraints = { } static mapping = { data type: JsonbMapType } }
The same criterias implemented for Json are valid for Jsonb. Besides that, there are some criterias that are only valid for Jsonb. Check the documentation.
With this criteria you can get all the rows that contain all the values in the map. To use it just use the criteria
pgJsonContains:
def obj1 = new TestMapJsonb(data: [a: 'foo', b: '1']).save(flush: true) def obj2 = new TestMapJsonb(data: [b: 1, d: '2']).save(flush: true) def obj3 = new TestMapJsonb(data: [a: 'foo', b: '1', c: 'test',]).save(flush: true) def result = TestMapJsonb.withCriteria { pgJsonbContains data, [a: 'foo', b: '1'] }
The previous criteria will return all the rows that contains all the keys/values ([a: 'foo', b: '1'] in the example)
in the data field. In this example will return obj1 and obj3.
With this criteria you can get all the rows that are contained by the values. To use it just use the criteria
pgArrayIsContainedBy:
def obj1 = new TestMapJsonb(data: [a: 'foo', b: '1']).save(flush: true) def obj2 = new TestMapJsonb(data: [b: 1, d: '2']).save(flush: true) def obj3 = new TestMapJsonb(data: [b: '1', a: 'foo', c: 'test',]).save(flush: true) def result = TestMapJsonb.withCriteria { pgJsonbIsContained data, [a: 'foo', b: '1', c: 'test'] }
The previous criteria will return all the rows that are contained in the map. In the example it will retun the objects
obj1 and obj3.
Sometimes you need to get some results ordered randomly from the database. Postgres provides a native function to do that. So you can write something like this:
select * from foo order by random();
The plugin now offers a new order method to do this random sorting:
import static net.kaleidos.hibernate.order.OrderByRandom.byRandom class MyService { List<TestMapJsonb> orderByRandom() { return TestMapJsonb.withCriteria { order byRandom() } } }
You may need to do a more complex sorting. Imagine that you have a table with a jsonb column and you want to order
by a field in that json. Using sql you can write:
select * from foo order by (data->'name') desc
With the plugin you can do the same with a new order method called sqlFormula:
import static net.kaleidos.hibernate.order.OrderBySqlFormula.sqlFormula class MyService { List<TestMapJsonb> orderByJson() { return TestMapJsonb.withCriteria { order sqlFormula("(data->'name') desc") } } }
It's important to note that the "raw" sql is appended to the criteria, so you need to be sure that it's valid because if not you'll get a sql error during runtime.
From 8.0.0 and forward release notes can be found on GitHub
| Version | Date | Comments |
|---|---|---|
| 7.0.0 | 29/Jul/2019 | Grails 4 (Hibernate 5.4): Add support for Grails 4 and Hibernate 5.4. Thanks to James Hardwick and Zhuravskiy Vitaliy. |
| 6.1.0 | 24/Sep/2018 | Grails 3 (Hibernate 5.2): Fix #30. Thanks to John Keith and jglapa. |
| 5.3.0 | 24/Sep/2018 | Grails 3 (Hibernate 5): Fix #30. Thanks to John Keith and jglapa. |
| 4.8.0 | 24/Sep/2018 | Grails 3 (Hibernate 4): Fix #30. Thanks to John Keith and jglapa. |
| 6.0.0 | 05/Jun/2018 | Grails 3: Add support for Hibernate 5.2. #114. Thanks to Alexey Zhokhov and Feng Yu. |
| 5.2.0 | 03/Nov/2017 | Grails 3 (Hibernate 5): Merged #107 and #109. |
| 5.1.0 | 22/May/2017 | Grails 3 (Hibernate 5): Change db credentials to make it compatible with Postgresql 9.6. |
| 4.7.0 | 22/May/2017 | Grails 3 (Hibernate 4): Change db credentials to make it compatible with Postgresql 9.6. |
| 5.0.1 | 21/May/2017 | Grails 3 (Hibernate 5): Fix #96. Thanks to jglapa. |
| 4.6.9 | 21/May/2017 | Grails 3 (Hibernate 4): Fix #96. Thanks to jglapa. |
| 5.0.0 | 07/Nov/2016 | Grails 3: Add support for Hibernate 5.1. Upgrade dialect to Postgresql 9.4, Grails to 3.2.2 and GORM to 6.0.3. |
| 4.6.8 | 03/Nov/2016 | Grails 3: Add support for generic Json/Jsonb criteria #95. Thanks to Sabst. |
| 4.6.7 | 01/Nov/2016 | Grails 3: Add UUID arrays. Thanks to Tom Potts. Fix #87 |
| 5.0.0-RC1 | 28/Oct/2016 | Grails 3: Add support for Hibernate 5. Thanks to Alexey Zhokhov and Eric Helgeson. |
| 4.6.6 | 24/Apr/2016 | Grails 3: Migrate (almost) all Java code to Groovy + @CompileStatic. No new features added. |
| 4.6.5 | 31/Dec/2015 | Grails 3: Fix #84. Starting Grails 3.0.10 the default sequence_per_table parameter was not working. |
| 4.6.4 | 29/Dec/2015 | Grails 3: Cleanup and new jar file with the same functionality as previous version. It seems that version 4.6.3 is corrupted. |
| 4.6.3 | 08/Dec/2015 | Grails 3: Add new criterias for Jsonb: contains and isContained. |
| 4.6.2 | 05/Dec/2015 | Grails 3: Cleanup old code for support Hstore in old Grails versions. |
| 4.6.1 | 02/0ct/2015 | Plugin migrated to Grails 3. |
| 4.6.1 | 21/Sep/2015 | Hibernate 4.x. Fix #76. |
| 4.6.0 | 08/Sep/2015 | Hibernate 4.x. Add support to order by a sql formula and by random. Fix #72. |
| 4.5.0 | 02/Jun/2015 | Hibernate 4.x. GR8Conf Hackergarten! Merge PRs: #62, #66, #67, #68, #69. |
| 3.4.0 | 02/Jun/2015 | Hibernate 3.x. GR8Conf Hackergarten! Add Jsonb support for Hibernate 3.x #64. |
| 4.4.0 | 15/Mar/2015 | Hibernate 4.x. Add support for Jsonb. |
| 3.3.0 | 18/Aug/2014 | Hibernate 3.x. Fix #49. Configure sequence per table or a global sequence for all tables. |
| 4.3.0 | 17/Aug/2014 | Hibernate 4.x. Fix #49. Configure sequence per table or a global sequence for all tables. |
| 3.2.0 | 02/Aug/2014 | Hibernate 3.x. pgJsonHasFieldValue criteria. |
| 4.2.0 | 28/Jul/2014 | Hibernate 4.x. pgJsonHasFieldValue criteria. |
| 3.1.0 | 25/Jul/2014 | Add JSON support for Hibernate 3.x. It's now possible to store and read domain classes with map types persisted to json. |
| 4.1.0 | 24/Jul/2014 | Add JSON support. It's now possible to store and read domain classes with map types persisted to json. |
| 4.0.0 | 18/Jul/2014 | Version compatible with Hibernate 4.x. |
| 3.0.0 | 18/Jul/2014 | Version compatible with Hibernate 3.x. |
| 0.9 | 16/Jun/2014 | Add new array criterias: pgArrayEquals, pgArrayNotEquals. |
| 0.8.1 | 24/Apr/2014 | Fix NPE when array is null. |
| 0.8 | 24/Apr/2014 | Added support for Double and Float arrays. Refactored the ArrayType to be used as a parametrized type. |
| 0.7 | Unreleased | New HstoreMapType and update plugin to Grails 2.2.5. |
| 0.6.8 | 22/Apr/2014 | Fix NPE in HstoreType. |
| 0.6.7 | 14/Feb/2014 | Support Java Arrays in criterias. |
| 0.6.6 | 14/Feb/2014 | New criteria pgArrayIsEmptyOrContains. |
| 0.6.5 | 13/Feb/2014 | Fix bug deleting instances with Hstore type. Thanks to Manuel Unno Vio! |
| 0.6.4 | 30/Jan/2014 | Convert automatically the keys of Hstore to string. |
| 0.6.3 | 19/Jan/2014 | Display the class name during startup when detecting a hstore property. |
| 0.6.2 | Unreleased | Refactor some tests. |
| 0.6.1 | 28/Nov/2013 | Update postgresql jdbc driver to version 9.2 and do not export hibernate plugin. |
| 0.6 | 21/Nov/2013 | Use a more complete Hstore parser. Thanks to Moritz Kobel! |
| 0.5.1 | 10/Nov/2013 | Change base directory to compile AST before the plugin classes. Thanks to Moritz Kobel! |
| 0.5 | 08/Nov/2013 | Add criteria operation for Hstore types. |
| 0.4.1 | Unreleased | Compile AST before the project itself. |
| 0.4 | 28/Oct/2013 | Add support to Hstore. It's only possible to save and get, but no queries has been implemented. |
| 0.3 | 18/Sep/2013 | Add support to define the schema name for the sequences. |
| 0.2 | 25/Aug/2013 | Support for arrays of Enums with automatic serialization/deserialization to ordinal integer value. Thanks to Matt Feury! |
| 0.1.1 | 22/Jul/2013 | Some refactors of the code. No functionality added. |
| 0.1 | 16/Jul/2013 | Initial version of the plugin with support for integer, long and string array types and criterias pgArrayContains, pgArrayIsContainedBy, pgArrayOverlaps, pgArrayIsEmpty and pgArrayIsNotEmpty. |