Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed readme #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions chill-db/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,12 @@ It is designed to be usable quickly, with code-only configuration.
class User extends chill.db.ChillRecord { // by default, maps to the `user` table

// define column mappings as fields, with all relevant metadata
Field<BigInteger> id = field$("id", BigInteger.class).autoGenerated$().primaryKey();
Field<Date> createdAt = field$("created_at", Date.class).createdAtCol();
Field<Date> updatedAt = field$("created_at", Date.class).updatedAtCol();
Field<BigInteger> id = field("id", BigInteger.class).autoGenerated().primaryKey();
Field<Date> createdAt = field("created_at", Date.class).createdAtCol();
Field<Date> updatedAt = field("created_at", Date.class).updatedAtCol();

Field<String> email = field$("email", String.class).required();
Field<String> password = field$("password", String.class).required();
Field<String> email = field("email", String.class).required();
Field<String> password = field("password", String.class).required();

public static final find = finder(User.class);

Expand Down Expand Up @@ -61,4 +61,4 @@ Query<User> matches = User.where("email like ?", "%chill%");
* Require no annotations
* Express all database metadata in code, in the model files, so you can see wtf is going on
* Be easily debuggable
* Show users wtf is going on at the JDBC level clearly via logging
* Show users wtf is going on at the JDBC level clearly via logging