From 2aab4e2b14140a68c3520e0a0d1b7185aa3521a9 Mon Sep 17 00:00:00 2001 From: brianc Date: Mon, 13 Dec 2010 12:53:00 -0800 Subject: [PATCH] notes/warning on not using directly Updated Connection (markdown) --- Connection.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Connection.md b/Connection.md index 1e0186c..dfc6fab 100644 --- a/Connection.md +++ b/Connection.md @@ -1,4 +1,8 @@ -The connection object is a 1 to 1 mapping to the [postgres client/server messaging protocol](http://developer.postgresql.org/pgdocs/postgres/protocol.html). The __Connection__ is mostly used by the [[Client]] but you can do anything you want with PostgreSQL using the connection object if you need some low level access. Let me know if you do use it directly as maybe what you're doing could be wrapped up in the [[Client]] api. I studied the protocol for a while implementing this and the documentation is pretty solid. If you're already familiar you should be right at home. Have 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) +The connection object is a 1 to 1 mapping to the [postgres client/server messaging protocol] + +#### Not recommended to directly instantiate this object under normal scenarios + +(http://developer.postgresql.org/pgdocs/postgres/protocol.html). The __Connection__ is used internally by the [[Client]]. Technically, you can do anything you want with PostgreSQL using the connection object if you required special lower level access. Let me know if you do use it directly as maybe what you're doing could be wrapped up in the [[Client]] api. I studied the protocol for a while implementing this and the documentation is pretty solid. If you're already familiar you should be right at home. Have 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) There are a few minor variations from the protocol: