Opened 7 years ago
Closed 7 years ago
#1673 closed enhancement (fixed)
RasdaPy_Exception should return error message from rasql
Reported by: | Bang Pham Huu | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 9.5 |
Component: | rasdapy | Version: | development |
Keywords: | Cc: | Vlad Merticariu, Dimitar Misev | |
Complexity: | Medium |
Description
Example query with incorrect interval
select c[2:0, *:*] from test_rasdapy_rgb as c
the error trace in RasdaPy misses the error message as in rasql
Traceback (most recent call last): File "/home/rasdaman/TEST/rasdapy/tests/test_crud.py", line 199, in test_07_read_wrong_interval data = ConfigManager.execute_read(rasql_query) File "/home/rasdaman/TEST/rasdapy/tests/test_crud.py", line 33, in execute_read res = query.eval() File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/core.py", line 435, in eval return self._execute_read() File "/home/rasdaman/.local/lib/python2.7/site-packages/rasdapy/core.py", line 479, in _execute_read exec_query_resp.token) Exception: Error executing query: err_no = 389, line_no = 1, col_no = 11, token = :
error from rasql query
rasql -q 'select c[2:0, *:*] from test_rasdapy_rgb as c' --out string Executing retrieval query... rasdaman error 389: Execution error 389 in line 1, column 11, near token :: No interval (in case of fixed bounds, the upper one can not be smaller than the lower one).
At least the error message in rasql can help one to understand error better.
Note:
See TracTickets
for help on using tickets.