So in a K8s deployment, this adds support for having an initial number of connections to create initially (higher that min connections). This allows for a smoother deployment, by effectively having initially more connections than min in order to immediately take production load, and then over time trim back down towards the min connections.
So in k8s I am setting min, initial and max connections, where initial connections is high enough to take full production load straight after readiness true.
* fix jackson NCDF error
split jackson SPI impl into it's own module
* Restore format
* Restore format
* Trim up dependencies
* Rename module to ebean-core-json
---------
Co-authored-by: Rob Bygrave <robin.bygrave@gmail.com>
It barfs trying to parse the 25-EA version, means the kotlin-querybean-generator fails the build for the Java Early Release versions.
With this, it will skip the kotlin modules for the Java Early Access release builds.
Note that this still supports Java 11.
The 10.0 version of ebean-datasource uses Multi-Version jar such that if running using Java 21+ then it will use Virtual Threads for the background Heartbeat validation and also background closing of connections.
The `@Column` length defaults to 0 rather than 255, this allows us to detect when it has been explicitly set and thus for Postgres we can now have:
@Column(length=255) mapping to -> varchar(255)
@Column mapping to -> varchar
ebean-test-containers version 7.6 supports extraDb for MySql and MariaDb, resolving #3511 with extraDb configuration for each extra schema/database required with MySql or MariaDb.
Currently, the SELF response type of QueryBuilder returns as Object when really we want it to return the SELF generic type of QueryBuilder, QueryBean, IQueryBean etc
Note that this change requires an updated ebean-agent
* Added modules `ebean-net-postgis-types`, `ebean-net-postgis` for new `net.postgis` geometry types without support for GeoLatte.
* Added missing `uses` entry in `module-info.java` for `io.ebean.api`.
Rob Bygrave