-
Notifications
You must be signed in to change notification settings - Fork 14
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
Updates the README with descriptions of Orville some sample code #338
Conversation
docs/README.md
Outdated
## Why Orville? | ||
|
||
Orville is not meant to replace existing PostgreSQL libraries in the Haskell | ||
ecosystem, but to complement them. It has the power to satsify most experienced |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
satsify -> satisfy
docs/README.md
Outdated
hand yet doesn't require absolute type-safety between your custom SQL | ||
statements result sets and the Haskell types they decode into, Orville may be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean "your custom SQL statements' result sets" here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really I think it should be "your customs SQL statements, their result sets and...". Thanks!
docs/README.md
Outdated
|
||
## Just show me some code! | ||
|
||
Ok! Here's a very simple application that inserts to entities of a `Pet` model and finds one of them based on its name. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the "to" here is unnecessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. It should probably say "inserts some entities" though rather than just "inserts entities"
{- | | ||
It's good practice to create newtype specific to each entity to hold its | ||
primary key value | ||
-} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
newtype -> newtypes; missing period at end of comment.
{- | | ||
Marshaller above is associated with the @pet@ table. The marshallers fields | ||
will define the column of the table. | ||
-} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
marshallers -> marshaller's; column -> columns
This is probably easiest to review by browsing files on the commit to merge here: https://github.com/flipstone/orville/tree/42fb5446cb5dd5f394cac1480b7fcf28642bb7e9