Add namespacing/modules about askql HOT 6 OPEN

On the other hand, what I think we could do is to have a way to return a MySQL object which has a number of fields, each of them being a function (e.g. field findOne being a function for finding a single row in a table etc.) and then run mysql.findOne().
Please note that here we use dot instead of the colon. In AskScript we used colon for the "method" syntax sugar and method chaining, but dot for accessing properties (see e.g. this sample .ask file: https://github.com/CatchTheTornado/askql/blob/master/src/askscript/__tests__/08-objects-records/objects-14-key_access.ask )

from askql.

... the simplest possible solution could be to extend the run() method on vm to let the officially registered resources return methods or return sub-resources (chaining) etc. we're not talking about the OOP methods - however this could potentially be a great solution too

from askql.

@pkarw , the issue I see here is that currently code like mysql:findOne() is just a syntactic sugar over findOne(mysql), which means that regardless what kind of variable mysql is, the very same findOne() function will be called.
The translation is not done in run() in vm, which is called when executing the parsed program, but much earlier - when parsing the AskScript source code into AST.

from askql.

This way we could have:

// mysql - a resource that has several fields with functions, e.g. connect 
conn = mysql.connect('host', 'user', 'pass')
conn.useDb('dbname')
row = conn.findOne('text to search for')

from askql.

@czerwinskilukasz1 good point. I think it's a great way to go for this FR; it's somewhat clarifying the #580 as well (I mean the "dot" notation could be used to have both #579 and #580 up)

from askql.

Blocked by #589

from askql.