FASM - Flat Assembler
17 May 2013A quick reminder post to myself to go and look at Flat Assembler. Interest was sparked initially from a article that was more of an x86 assembly tutorial here
A quick reminder post to myself to go and look at Flat Assembler. Interest was sparked initially from a article that was more of an x86 assembly tutorial here
Testing is a large component of any software development done, sometimes though - you don’t want to go through a full unit test suite just to see what a REST service is doing. I’ve come across some interesting concepts with cURL that will certainly be a shortcut benefit to seeing what responses your REST services are returning.
You can simulate all of the different HTTP verbs against any URL you’d like using cURL with the following syntax at the console:
# Retrieve person (id: 1)
$ curl -i -X GET http://localhost/service/people/1
# Retrieve all people
$ curl -i -X GET http://localhost/service/people
# Delete person (id: 1)
$ curl -i -X DELETE http://localhost/service/people/1
# Create a new person
$ curl -i -X POST -H 'Content-Type: application/json' -d '{"first_name": "John", "last_name": "Smith"}' http://localhost/service/people
# Modify a person (id: 1)
$ curl -i -X PUT -H 'Content-Type: application/json' -d '{"first_name": "Jane", "last_name": "Smith"}' http://localhost/service/people/1A small list of video library links on the topic of Haskell are accumulating in my inbox, so I thought I’d compile them here for viewing later.
Sometimes having the power of MapReduce at your fingertips and applying this technology to simpler aggregate queries can be more hassle than it needs to be. MongoDB provides a simpler solution (for a simpler class of problems) in the form of the Aggregation framework. This framework allows you to develop queries within the mongo environment that are analogous to GROUP BY, HAVING, COUNT, SUM, etc. that you would normally use in “relational land”.
Today’s post, I want to walk through a couple of simple queries on using this framework to maximise productivity when pivoting data.
As a bit of a cheat’s reference, the following table provides the some examples of aggregate queries in a relational database and how they transpose over to the Mongo aggregation environment.
The source of this table can be found here.
| Technique | Relational | Aggregation Framework |
|---|---|---|
| Criteria matching | WHERE | $match |
| Grouping | GROUP BY | $group |
| Aggregate criteria filtering | HAVING | $match |
| Result projection | SELECT | $project |
| Record sorting | ORDER BY | $sort |
| Limiting result sets | LIMIT or TOP | $limit |
| Accumulation | SUM | $sum |
| Counting | COUNT | $sum |
| Dropping | SKIP | $skip |
Sql example:
SELECT COUNT(*) AS count
FROM itemsMongo example:
db.items.aggregate( [
{ $group: { _id: null,
count: { $sum: 1 } } }
] )Sql example:
SELECT SUM(price) AS total
FROM itemsMongo example:
db.items.aggregate( [
{ $group: { _id: null,
total: { $sum: "$price" } } }
] )Sql example:
SELECT category_id, SUM(price) AS total
FROM items
GROUP BY category_idMongo example:
db.items.aggregate( [
{ $group: { _id: "$category_id",
total: { $sum: "$price" } } }
] )Sql example:
SELECT category_id, SUM(price) AS total
FROM items
GROUP BY category_id
ORDER BY totalMongo example:
db.items.aggregate( [
{ $group: { _id: "$category_id",
total: { $sum: "$price" } } },
{ $sort: { total: 1 } }
] )Sql example:
SELECT category_id, when SUM(price) AS total
FROM items
GROUP BY category_id, whenMongo example:
db.items.aggregate( [
{ $group: { _id: { category_id: "$category_id",
when: "$when" },
total: { $sum: "$price" } } }
] )Sql example:
SELECT category_id, count(*)
FROM items
GROUP BY category_id
HAVING count(*) > 1Mongo example:
db.items.aggregate( [
{ $group: { _id: "$category_id",
count: { $sum: 1 } } },
{ $match: { count: { $gt: 1 } } }
] )Sql example:
SELECT category_id, when, SUM(price) AS total
FROM items
GROUP BY category_id, when
HAVING total > 100Mongo example:
db.items.aggregate( [
{ $group: { _id: { category_id: "$category_id",
when: "$when" },
total: { $sum: "$price" } } },
{ $match: { total: { $gt: 100 } } }
] )Sql example:
SELECT category_id, SUM(price) AS total
FROM items
WHERE active = 1
GROUP BY category_idMongo example:
db.items.aggregate( [
{ $match: { active: 1 } },
{ $group: { _id: "$category_id",
total: { $sum: "$price" } } }
] )Sql example:
SELECT category_id, SUM(price) AS total
FROM items
WHERE active = 1
GROUP BY category_id
HAVING total > 100Mongo example:
db.items.aggregate( [
{ $match: { active: 1 } },
{ $group: { _id: "$category_id",
total: { $sum: "$price" } } },
{ $match: { total: { $gt: 100 } } }
] )Sql example:
SELECT category_id, SUM(co.weight) AS weight
FROM items i, components co
WHERE co.item_id = i.id
GROUP BY category_idMongo example:
db.items.aggregate( [
{ $unwind: "$components" },
{ $group: { _id: "$category_id",
weight: { $sum: "$components.weight" } } }
] )Sql example:
SELECT COUNT(*)
FROM (SELECT category_id, when
FROM items
GROUP BY category_id, when) AS Table1Mongo example:
db.items.aggregate( [
{ $group: { _id: { category_id: "$category_id",
when: "$when" } } },
{ $group: { _id: null, count: { $sum: 1 } } }
] )Coming from a relational database background, technologies such as stored procedures and user defined functions have always helped out when building a database infrastructure. MongoDB provides the same sort of code storage in stored javascripts in the database.
Creating a stored javascript into a database is a straight forward process of adding an item to the system.js collection.
> db.collection.js.save({_id: "greaterThan10",
... value: function (x) { return x > 10 }});Ok, this isn’t the most useful of functions. We’re testing if the value passed in the greater than 10. We’re able to use this in queries of our own using $where syntax like so:
> db.people.find({$where: "greaterThan10(this.age)"})This would get all of the “people” documents out of the database where they were over the age of 10. This is quite verbose of such a simple example, but you can see that by filling out the function in the saved javascript with more complex operations, you could achieve a lot with a little.
Working with the collection as usual, you can simply remove your stored javascript by id.
> db.collection.js.remove({_id: "greaterThan10"})As a final note, once you’ve created your stored javascript you can test it using eval easy enough.
> db.eval("return greaterThan10(9);")
false
> db.eval("return greaterThan10(11);")
trueThis is just a short introduction into the world of stored javascripts. The internal workings of MongoDB is all based on javascript, so it’s a good idea to have your skills nice and sharp before going in!