bigeasy / relatable Goto Github PK

Use project name in README.

We'll support AND, but nothing more complicated than that. You can further winnow the result set in the where clause.

Include AND in ON logic. Currently, you're able to use AND to join against one to one selects, but not sub-selects.

Currently using underbars, but dots would preserve case, be invalid SQL.

Create a README.md with examples and exposition.

Instead of specifying additional selects in subsequent select statements, define them in the select clause. If a sub-select returns more than one field, it will be run as a subsequent select.

Need to review Proof and compare its teardown patterns to the patterns implemented here. Will also rename harness._coffee to to proof._coffee while I'm at it.

Things to do along the way.

• Stop the initial scan in compiler after you've reached the last of table.

Nope. Not going to do that.

Convert the test to Proof and follow the latest Proof conventions.

Any test, to see how long a single test takes.

The API needs to be able to accommodate Node.js developers working in JavaScript.

Not positional parameters (yet) but named parameters.

Need to add support for schemas. I use them all the time now in PostgreSQL.

Use this issue to track progress of pre-release development.

Relatable will be read for use with a version 0.2.0 release for developers who are able to keep up with a project in development. When 0.2.0 is released, Relatable will follow the same release pattern as Node.js, with the even number indicating a API frozen maintenance branch, while development continues on the odd number one less than the even number.

That is, when 0.2.0 is release, the 0.2 version branch will be API frozen. Development will continue on 0.1 toward a 0.4.0 release. When 0.4.0 is released, it will be API frozen. The 0.3 branch will become the development branch. We continue in this fashion until a version 1.0.

Prior to the 0.2.0 release, if you decide to adopt the pre-release 0.0 branch, please use NPM and package.json to freeze a version of Relatable that works for you. Follow this issue for updates on changes. Read the change log to know how an update will affect your application.

When 0.2.0 is released semantic versioning takes over. Even numbers are API stable, odd numbers are API playgrounds. At 0.0, however, everything is in flux. Up is down. Left is right. Callbacks are synchronous. Cats like baths. Early adoption is welcome, because it helps build a better library, but please be patient and please be careful.

Connection errors during select go unreported.

I was expecting that creating a mutation would open a transaction.

To further convert from CoffeeScript, de-dent your object definitions.

Simply does not work.

Support only named parameters in calls to select.

While you're at it, remove the need to pass in a context.

Need to review Proof and the current harnesses to determine what the latest teardown pattern is and apply that pattern.

Move all files to the top level directory.

Create a default underbarred to camel case translation followed up by ways of composing exceptions including acronyms and explicit mappings.

var base = startHere();
var acronyms = acronymed('npm ip ssn', { case: 'lowered' }, base);
var maps = mapped({ foo_bar_fbn: "fooBarFBN" }, acronyms);

For now, we are going to assume a case insensitive data dictionary.

I'm open to discussing case sensitivity. Support for quoting would need to be added to the SQL pre-processor. There have been times when I've inherited a database from someone who built the database using a drag and drool interface that generated DDL such that TK_Employee_Job_Position would forever been capitalized just so. When I encounter this again, I'll probably want to support quoted identifiers myself, but until then I'm going to assume that DDL is created by a tool or person aware of SQL traditions.