Welcome to PikaORM
The lightweight MicroORM for Java — no config files, no magic, just clean builder-style API over plain SQL.
ORM ⚡
Ahh yes, just what we need: another ORM…. But hear us out — Pika is different.
The Need-To-Know Essentials
Before you scurry 🐁💨 off to your first project, here are the things you need to know about Pika:
1. Concision is king.
Pika approaches the ORM problem with radical simplicity:
- No config files.
- Intuitive builder-method based API design that is all code.
- Vast customizable mappings/models/features all using plain Java classes.
- Easy to understand code base for personal modification.
2. Pika doesn't hide much SQL from you
If you cannot do something simplistically with Pika logic, you are encouraged to use raw SQL — you are given many ways to do this!
3. Pika has two flavors of database mapping features.
A more SQL-native paradigm, and a POJO (Plain Ole' Java Objects) object-leaning side. These are by no means exclusive features in usage — in fact you are encouraged to use both ideas for different things!
Pika is
- A zero-config, builder-style ORM
- SQL-transparent and honest
- Easy to drop into any Java project
- A lightweight foundation you can extend
Pika isn't
- A full-scale Hibernate replacement
- An annotation processor or code generator
- Magic — you always see the SQL
- Trying to be everything to everyone
Found below are all the quick starts one would need to jump straight into Pika usage with their given database type in a web application. NOTE: We will take requests and changes for specific database types at our own discretion!
Supported Databases
- SQLite (Use
.sqlLiteQuirks()on ORM configuration — most native to PikaORM) - H2 (In Memory, Oracle, PostgreSQL, SQLServer modes)
- MariaDB (Has some small problems with
insertAll— maybe avoid!)
Are you looking at all of this going, what does this all mean — why and what is an ORM? Check out our super uber beginner guide to get started, I promise it's not that tough :)