mgm | Mongo Go Models is a fast and simple MongoDB ODM | SQL Database library

It looks like your property 'vasco-LinkUserToDPToken' is a multivalued property type (string array) of which you need to extract the DN inside.

You could try:

Not sure where the problem lies, so excuse the lengthy explanation on SQL->JPQL:

1. Replace your table names with your entity names

   • movement_group -> MovementGroup

2. Replace your joins with the java references, letting JPA use the relationship mapping you've defined instead.

   • "join movement_group_mean mgm on m.id = mgm.movement_group_id" becomes "join m.movementGroupMeans mgm"
   • "join movement_mean mm on mgm.movement_mean_id = mm.id becomes "join mgm.movementMean mm"

Only tricky spot is your entities do not define a basic mapping for the marina_id value. So to get at m.marina_id, you will have to use the 'marina' reference and use its presumably ID value: "m.marina_id = :marinaId" -> "m.marina.id = :marinaId"

Giving you JPQL:

Luis Miguel Mejía Suárez's comment worked perfectly and was the easier approach.

In the context of this project, all I had to do was:

1. Append -SNAPSHOT to the version in /version.sbt (should not be needed normally but for this project I had to do this)
2. Run sbt publishLocal in the parent project.

After this, the example project (which already targets the -SNAPSHOT version) is able to pick up the locally built package.

You can use startswith() and any() together to filter out the dictionaries you don't want:

You can do droplevels(dftest$Studio) to remove unused levels

That is the correct desired result. So though your stream returns the proper value, the stream builder first gets null before your stream gets data. So if you don't want to show NoDataRelatedLocation before your stream gets real data, you should put initialData param of your stream builder.

You can try applying these styles:

You can add the fuzziness parameter to your query, like this:

I hope this counter example helps.