Opened 7 years ago
Closed 7 years ago
#1671 closed defect (fixed)
RasdaPy_Update collection query should be executed as update query
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.5 |
Component: | rasdapy | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description
There is a problem with checking which rasql query should run with read/write permission in RasdaPy.
Here is the problem code:
https://github.com/thunderboltsid/rasdapy/blob/master/rasdapy/core.py#L425
a update collection query like this
UPDATE test_rasdapy_mr SET test_rasdapy_mr[0:255,0:210] ASSIGN shift(decode(<[0:0] 1c>, "GDAL", "{\"filePaths":[\"/home/rasdaman/TEST/rasdapy/tests/mr_1.png\"]}"), [0,0])
is considered as read query.
Also, this code needs to be fixed to make the comparison insensitive as in rasql (e.g: SELECT, seLECT, select,…) are valid cases.
It also missed the SELECT INTO which is an update query not read query.
Change History (2)
comment:1 by , 7 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:2 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.