Jens Schauder

I would put this check in the `JdbcAggregateTemplate` or in the classes called by it. Putting it in the `JdbcRepositoryFactory` hat two problems: 1. It would prevent people from (ab)using...

Yes, a PR would be the next step. And yes that is the correct document for guidance. But we are already did a lot of the stuff (like discussing changes...

While it is not really consistent with the repository abstraction, I still think we should make it work.

@mp911de I'd like your opinion on this.

@kodstark While I strongly recommend against using different databases in test and production (use Testcontainers instead) Spring Data JDBC supports running against the two databases just fine, as long as...

@Xiphoseer > The forceQuote property is actually a bit of a misnomer -- what it does is set SqlIdentifier#quoted which in turn acts more like `enableIdentifierProcessing` when `SqlIdentifier#toSql` is called....

It depends on your actual requirements. There is `@ReadOnlyProperty` which marks a property as not to be used during insert or update operations. Of course that is not dynamic and...

This should be implemented as using an attribute of the `@Column` annotation, similar to [Spring Data MongoDbs `@Field.write`](https://docs.spring.io/spring-data/data-mongodb/docs/current/api/org/springframework/data/mongodb/core/mapping/Field.html#write())

The same problem probably appears for standard `CrudRepository` methods like `findAll` and `findById` and so on. I think we should have some way to configure the [Memoization](https://en.wikipedia.org/wiki/Memoization) of SQL statements...

Are we talking about Spring Data JDBC? Because you use `@Embeddable` which is not a Spring Data JDBC annotation and `@Embedded` can not be used without value for `oneEmpty`. This...