Data and vtables vs. objects and methods
This is the first time I have heard "vtabels", the more known term is decision table. Also, on the contrary, using decision tables is very idiomatic JavaScript and is used often, just rarely with lambdas and more often with named functions.

Also, your rows array (is this a global intentionally?) uses rows implying it's a row where every element is a single object.

That said, JavaScript has functional methods like Array.prototype.map, Array.prototype.filter and Array.prototype.reduce. 

You can use those to map, filter and reduce things.

For example, your code (assuming it sums ages) could be written as:

var rows = [{id: 0, name: "Alice", age: "23"},
            {id: 1, name: "Bob", age: "25"} /* ... */];

var ageSum = rows.reduce(function(accum,next){return (+next.age)+accum},0);
ageSum; //48


Given the more functional style, your SQL WHERE becomes .filter

rows WHERE name = 'Bob'


Becomes:

rows.filter(function(name){
    return name==="Bob";
})


Similarly, aggregators become .reduce and mappings (and joins) become .map.