Turn off logging of what MySQL session store is doing.

Instead enable logging of HTTP requests that our express server gets.

Simple initial implementation.

Responds to auth and comments_meta requests.

With /auth we always respond with false.

With /comments_meta we only return comment counts.

Make the data structure the same as in old comments app.

On error the rows will be null, so do a check before calling rows[0].

Finally understood why it's the convention in NodeJS.
So following it now.

I assume this is more along the lines how things are done in NodeJS.

So the actual interfacing with node-mysql is contained within that
class.

The :jasmine task now populates comments_test with test data and
then runs the testsuite against it.

The script update_votes.sql calculates the values for that column based
on the entries in votes table.

This is an optimization to avoid aggregating the votes in a separate
table every time we retrieve comments.

Also updated examples.sql to use the new full_visible_comments view -
this greatly simplified all queries.

Include jasmine-node into our comments backend dependencies.

Write comments.spec.js to test all methods in Comments class.
For now we're using the actual full database - must replace with a test
database.

Add :jasmine task to Rakefile.

It also turned out that I can't have comments inside package.json.
So I need to remove those helpful comments from there... great.

Also add full_visible_comments view to simplify the queries.

Finally added a small test script to check if it's actually working.

Results in better error messages.

A strange 'unknown' target has NULL fields otherwise.

MySQL has restriction for index size, so make the fields shorter.
100 should be enough for class and member names.
50 should be enough for domain name.

We'll delete these targets later, but for now I want to be able to
insert them.

I though Date.parse() returns a date, but it returns milliseconds
instead.