scalikejdbc | tidy SQL-based DB access library | DB Client library

I'm not familiar with Scala, but you definitely can't use PGobject with H2, this class is specific to PgJDBC. To pass a JSON value to H2, you need to use a plain byte array (byte[] in Java, Array[Byte] in Scala); the passed array should contain JSON text in UTF-8, UTF-16, or UTF-32 encoding. You can also use a java.lang.String if you wish, but it will require FORMAT JSON clause in SQL after parameter.

To read a JSON value from H2 it would be better to use ResultSet.getBytes(…) in Java/JDBC and WrappedResultSet.bytes(…) in ScalikeJDBC, it will return byte array with JSON text in UTF-8 encoding. Currently you're using a string(…) method, it should work too at least with H2 1.4.200, but such behavior is not documented and may be changed in the future releases.

These suggestions are for builtin JSON data type of H2.

The sbt-assembly plugins shade rule ShadeRule.keep documentation states

The ShadeRule.keep rule marks all matched classes as "roots". If any keep rules are defined all classes which are not reachable from the roots via dependency analysis are discarded when writing the output jar.

https://github.com/sbt/sbt-assembly#shading

So in this case all the classes of the class path x.* and FooBar.* are retained while creating the fat jar. Rest all other classes including the classes in scala-library are discarded.

To fix this remove all the ShadeRule.keep rules and instead try ShadeRule.zap to selectively discard classes not required.

For example, the following shade rules removes all the HDFS classes from the far jar:

This is not an error, it is an internal debug message from the AWS SDK. It is logged here, and if you look a few lines above you'll see this comment:

You are mapping your result records to a Map. A Map does not guarantee the order of the keys, hence every call will return result-set in different order.

You can map your result-set to a case class in the following way:

In general, AutoSession behaves as an auto-commit session for DDL and the insert/update/delete ops whereas it works as a read-only session for select queries.

It seems to be doing as follows is the straight-forward way.

The parameter name in Databases.inMemory must match the folder under evolutions.

For example, if the evolutions are in evolutions/default/*.sql, then you must call Databases.inMemory(name="default", db).

In general, you should convert all of your different results to your "most general" type that has a monad. In this case, that means you should use OptionT[IO, A] throughout your for-comprehension by converting all of those IO[Entity] to OptionT[IO, Entity] with OptionT.liftF:

I think I found something, but it is for Python: https://github.com/RDFLib/sparqlwrapper

I need something for Scala or Java 8+.

I don't know a lot about PostgreSQL's jsonb type, but it seems impossible to pass everything as bind parameters in a JDBC PreparedStatement. I have to say that you may have to use SQLSyntax.createUnsafely to bypass PreparedStatement as below: