Renato Cavalcanti
Renato Cavalcanti
do we have it automated for other 'satellite' projects?
@nvollmar, we will need MiMa exclusions.
Hi @rrevi, Thanks for reporting this. You are correct on your comment in the [discuss forum](https://discuss.lightbend.com/t/akka-persistence-ora-00942-table-or-view-does-not-exist/8085/6?u=octonato). `oracle-schema-overrides.conf` is fixing this, but that only happens in our tests. Which also explains...
@WellingR / @otobrglez It would be create to have Json DAO. Even better if they are not bound to any specific Json lib (json4s, play-json, circe), but configurable by passing...
Oh, I just realised one thing. The current implementation doesn't have a dedicated column to store the payload + the manifest. It serializes a `PersistentRepr` in which the payload for...
To be honest, I fear that we will add lots of complexity to support this: custom table + different DAOs. But I may be wrong. That's just my first impression.
@PerWiklander, it's not enough to change the column to `json`, when persisting, the plugin must keep the payload as json. I think you can achieve what you want by defining...
Why would we create a new config property? We have already `maxConnections`. Moreover, what I see on Slick code base is that when using Hikari, `maxConnections` is used to configure...
I will fill an issue on Slick + PR for this. On our side, the workaround would be to use `maxConnections` to configure the DS using JNDI and propagate that...
Filled issue in Slick project: https://github.com/slick/slick/issues/1814 and corresponding PR: https://github.com/slick/slick/pull/1815