Configurable row limit about bbqsql HOT 7 CLOSED

It currently tries to detect the number of rows. Is this not working? If
you build out a query where the idea of col-index makes sense, there is no
reason why you couldn't drop row-index into that part of your query. What
happens if you don't specify row-index?

Ben Toews

On Nov 5, 2012, at 17:49, Greg Ose [email protected] wrote:

If we only have n rows to query, only iterate that amount on row_index. For
example, if I know I have 1 row in my result set, it should only iterate
the column index.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/39.

from bbqsql.

I tested with no row-index. I had the same col-index being tested ~6 times across different threads, in a single threaded test it appeared to iterate the col-index without repeats for row-index.

from bbqsql.

Okay. I thought you were talking about iterating over db columns. Would it
be an okay fix if I just had it handle the no-row-index case better? I
don't know how I feel about adding an option to specify max rows. The other
use case for this would be if people only wanted to dump the first 100 rows
or something, but that would be better addresses by just adding a limit in
the query. What do you think?

Ben Toews

On Nov 5, 2012, at 19:05, Greg Ose [email protected] wrote:

I tested with no row-index. I had the same col-index being tested ~6 times
across different threads, in a single threaded test it appeared to iterate
the col-index without repeats for row-index.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/39#issuecomment-10095402.

from bbqsql.

Seems reasonable, no row-index in the query -> no iteration across rows. I think it would be useful to add an optional max row / column to the template syntax, ${char/row_index:start:end?}?

from bbqsql.

I feel like the gevent portion of this app is a disaster. I might wait to fix this until I can do a re-write of the techniques. py file.

from bbqsql.

What's not working in techniques.py?

from bbqsql.

the whole thing is just ugly and over complicated

from bbqsql.