Joist is an ORM based on code generation.
The goal is to provide Rails-like "empty domain objects" in an ORM that is simple, pleasant to use, and scales nicely to really large schemas.
See joist.ws for more information.
The Joist test suite requires running tests against a local database; to use MySQL for this:
-
Edit
features/build.properties
(which is not checked in) and set your local MySQL passwordOn a clean ~18.04 Ubuntu, see this SO answer to set your local
root
password. -
Run
./gradlew install
The Joist test suite requires running tests against a local database; to use Postgres for this:
-
Edit
features/build-pg.properties
(which is not checked in) and set your localpostgres
user/admin passwordOn a clean Ubuntu, Postgres's admin user/password is configured by:
sudo -u postgres psql postgres
and then\password postgres
to set your local admin password- In
postgresql.conf
ensurelisten_addresses
is set
-
Edit
features/.../Registry.java
and change thedb
field toDb.PG
-
Edit
features/.../JoistCli.java
and change thedb
field toDb.PG
-
Run
./gradlew install
Note that because of Postgres's ability to defer FK constraints, the features/.../codegen
output will all change as the MySQL version is currently checked-in.
- Composite columns (e.g. TimePoint with both time+zone), if needed
- Don't muck with system properties
- Repo interfaces
- Implement stub that copies values (iterates Alias,
toJdbcValue
,ArrayList<Object>
) - Only one commit/flush at a time, serialized transaction isolation, leverage op locks
- Implement stub that copies values (iterates Alias,
- Configuration option (global, per-collection) to disable collection ticking
- ...maybe remove/solve annoyance of cross-collection stomp?
- Document PostgreSQL/MySQL no fsync settings for faster tests