Opened 13 years ago
Last modified 11 years ago
#127 closed enhancement
A double oid printed by rasql — at Initial Version
Reported by: | Owned by: | Heinrich Stamerjohanns | |
---|---|---|---|
Priority: | major | Milestone: | Future |
Component: | rasserver | Version: | 8.3 |
Keywords: | Cc: | Peter Baumann, Dimitar Misev | |
Complexity: | Very Hard |
Description
I am getting a weird behaviour from the oid operator in rasql,
suddenly it gives a non integer oid value for all collections (it is
the same for every collection I tested).
$ rasql -q "select oid(t) from MOD_WATERVAPOR_32633_1000 as t" --out string rasql: rasdaman query tool v1.0, rasdaman v8 -- generated on 31.01.2012 17:14:19. opening database RASBASE at localhost:7001...ok Executing retrieval query...ok Query result collection has 1 element(s): Result element 1: 2.37934e-317 rasql done.
After restarting the server with:
stop_rasdaman.sh start_rasdaman.sh
everything gets back to normal
$ rasql -q "select oid(t) from MOD_WATERVAPOR_32633_1000 as t" --out string rasql: rasdaman query tool v1.0, rasdaman v8 -- generated on 31.01.2012 17:14:19. opening database RASBASE at localhost:7001...ok Executing retrieval query...ok Query result collection has 1 element(s): Result element 1: 213505 rasql done.
It would appear to be an issue only for the oid() operator and
displayed output since a different query based on oid works as
expected:
rasql -q "select csv(m[0:10,0:10]) from mr as m where oid(m)=31745" -- out string
But in the meantime anything relying on getting oids with select
breaks.
Note:
See TracTickets
for help on using tickets.