Skip to content

Commit 32c4934

Browse files
committed
updated readme (again)
1 parent e6ae693 commit 32c4934

1 file changed

Lines changed: 6 additions & 5 deletions

File tree

README.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ So...__boom__. I set out to write my own. I'm not working on anything
2626
else in my spare time other than this. It's a labor of love. I'd
2727
love for you to love it as well. Contribute. Fork, patch, and send
2828
me a pull request. All I ask is everything you add you have complete
29-
and possible obsessive test coverage to back up.
29+
and possibly obsessive test coverage to back up.
3030

3131
## ALPHA version
3232

@@ -36,13 +36,14 @@ only refactoring after tests are in place.
3636

3737
### Connection
3838

39-
The connection object is a 1 to 1 mapping to the [messaging
40-
protocol](http://developer.postgresql.org/pgdocs/postgres/protocol.html).
41-
It is mostly used by the Client object (which...I haven't yet
39+
The connection object is a 1 to 1 mapping to the [postgres
40+
client/server messaging protocol](http://developer.postgresql.org/pgdocs/postgres/protocol.html).
41+
The __Connection_ object is mostly used by the Client object (which...I haven't yet
4242
finished implementing) but you can do anything you want with PostgreSQL using
4343
the connection object if you're really into that. I studied the
4444
protocol for a while implementing this and the documentation is pretty
45-
solid.
45+
solid. If you're already familiar you should be right at home. Have
46+
fun looking up the [oids for the datatypes in your bound queries](http://github.com/brianc/node-postgres/blob/master/script/list-db-types.js)
4647

4748
There are a few minor variations from the protocol:
4849

0 commit comments

Comments
 (0)