postgresql-http-server - npm Package Compare versions

Comparing version 0.2.0 to 0.3.0

package.json

		{
		"name": "postgresql-http-server",
		"version": "0.2.0",
		"version": "0.3.0",
		"author": "Björn Harrtell <bjorn@wololo.org>",
		@@ -8,3 +8,3 @@ "description": "PostgreSQL HTTP API Server",
		"bin": "bin/postgresql-http-server",
		"main": "lib/cli",
		"main": "lib/cli.coffee",
		"preferGlobal": "true",
		@@ -26,2 +26,3 @@ "repository": {
		"pg": "0.7.2",
		"sql-parser": "0.4.0",
		"log": "1.3.0"
		@@ -28,0 +29,0 @@ },

README.md

		@@ -25,2 +25,3 @@ # PostgreSQL HTTP API Server
		--password PostgreSQL password
		--cors Enable CORS support [boolean]
		--help Show this message
		@@ -31,21 +32,40 @@
		The API is discoverable which means you can access the root resource at /
		and follow links to subresources from there. But lets say you have a database
		named testdb with a table named testtable in the public schema. You can then
		and follow links to subresources from there but lets say you have a database
		named testdb with a table named testtable in the public schema you can then
		do the following operations:

		GET row data at:
		/db/testdb/schemas/public/tables/testtable/rows

		GET row data with where filter like:
		/db/testdb/schemas/public/tables/testtable/rows?where=id%3D3

		GET paginated row data with limit and offset params:
		/db/testdb/schemas/public/tables/testtable/rows?limit=10&offset=10

		GET a single row at:
		Retrieve (GET) or update (PUT) a single row at:
		/db/testdb/schemas/public/tables/testtable/rows/id

		POST a new row at:

		Retrieve rows (GET), update rows (PUT) or create a new row (POST) at:
		/db/testdb/schemas/public/tables/testtable/rows

		The default and currently the only dataformat is JSON.
		The above resources accepts URL encoded parameters where, limit and offset
		where applicable. Example:

		GET a maximum of 10 rows where cost>100 at:
		/db/testdb/schemas/public/tables/testtable/rows?where=cost%3E100&limit=10

		The default and currently the only dataformat is JSON. POSTing or PUTing
		expects a single JSON object with properties corresponding to column names.

		## TODOs

		* Use real primary key (current single row operations assume a primary key named id)
		* Optionally use authenticated user/password to connect to DB
		* Handle ORDER BY via orderby param
		* Handle PostGIS data
		* Allow raw SQL queries?
		* Handle DDL stuff?

		## License

		The MIT License (MIT)

		Copyright (c) 2012 Björn Harrtell

		Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

		The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

		THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

test.json

		{
		"name": "hello"
		"name": "hello53s"
		}

lib/cli.coffee