interpret table names in context of mountPath and basePath (Fixes #198)

That’s correct and I *thought* was somewhat clear. I added a note about the output path being absolute, which it is.

On Aug 17, 2014, at 18:10, John A. De Goes <notifications@github.com> wrote:

> In README.md:
> 
> > @@ -87,7 +87,9 @@ The server launches a simple JSON API.
> >  
> >  ### POST /query/fs/[path]?out=tmp231
> >  
> > -Executes the specified SQL query at the specified path. Returns the name where the results are stored.
> > +Executes a SQL query, contained in the request body, on the backend responsible for the request path. 
> > +Names mentioned in the query, as well as the output path, are interpreted as relative to the request path,
> > +unless they begin with `/`. Returns the name where the results are stored.
> 
> It's not clear if out can be a path or just a file name, and it's not clear if it should be an absolute path or a relative path (or both), and also what the interpretation of that absolute / relative path is given the base path.
> 
> Probably, if the out is relative, it should be interpreted with respect to [path], while if it's absolute, it should retain it's absolute positioning semantic. This is consistent with how paths appear in the query itself.
> 
> In any case, path returned by this method should probably be absolute to avoid any confusion.
> 
> —
> Reply to this email directly or view it on GitHub.
>