Pearu Peterson

This issue requires a test of the SQL `HAVING` clause as an example that triggers multiple steps of query executions.

Actually, any composite test would trigger multiple steps of query executions. For instance, ``` select bar(out0) from table(foo(cursor(select x from mytable))) ``` that involves three execution steps: 1. `select x...

https://github.com/omnisci/omniscidb-internal/pull/5134 might have a fix. Require verification.

This issue has likely the same origin as #77

Slack discussion https://quansight.slack.com/archives/C01CAU0U1FH/p1605528413113400 : Currently, rbc is able to make a decision if a UDF/UDTFs can be run on GPU or not based on the functionality used in LLVM IR....

Need an example demonstrating how to delete a UDTF.

Ideas from https://quansight.slack.com/archives/C9U5ZTWHX/p1605204779279400?thread_ts=1605197922.270000&cid=C9U5ZTWHX 1. Here is one idea that replaces the row element argument with the column buffer and row index pair in a UDF: ``` @omnisci('double(Column, rowindex)') def getitem(x,...

The recommended workflow that demonstrates the issue is: ``` In [1]: import rbc In [2]: import numba In [3]: at = rbc.typesystem.Type('int32[]') In [4]: target_info = rbc.targetinfo.TargetInfo.host() In [5]: rt...

The current state is: ``` In [19]: rt = rbc.typesystem.Type.fromnumba(numba.int32[:], target_info) --------------------------------------------------------------------------- NotImplementedError Traceback (most recent call last) in ----> 1 rt = rbc.typesystem.Type.fromnumba(numba.int32[:], target_info) ~/git/xnd-project/rbc/rbc/typesystem.py in fromnumba(cls, t, target_info)...

Marked as code quality because it would be nice for the completeness of the typesystem if ``` rt = rbc.typesystem.Type.fromnumba(numba.int32[:], target_info) ``` would work. Otherwise, this is not required for...