Changes between Initial Version and Version 2 of Ticket #127
- Timestamp:
- Feb 28, 2012, 1:39:17 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #127
- Property Reporter changed from to
- Property Summary A double oid printed by rasql → Change datatype of OId to long
-
Ticket #127 – Description
initial v2 1 I am getting a weird behaviour from the oid operator in rasql, 2 suddenly it gives a non integer oid value for all collections (it is 3 the same for every collection I tested). 1 OIds in rasdaman internally are represented as floating points, and it would be much better if they are actually integers. From a quick search, it seems like it might be sufficient to modify this 4 2 {{{ 5 $ rasql -q "select oid(t) from MOD_WATERVAPOR_32633_1000 as t" --out 6 string 7 rasql: rasdaman query tool v1.0, rasdaman v8 -- generated on 8 31.01.2012 17:14:19. 9 opening database RASBASE at localhost:7001...ok 10 Executing retrieval query...ok 11 Query result collection has 1 element(s): 12 Result element 1: 2.37934e-317 13 rasql done. 3 typedef double OIdPrimitive; 14 4 }}} 15 After restarting the server with: 16 {{{ 17 stop_rasdaman.sh 18 start_rasdaman.sh 19 }}} 20 everything gets back to normal 21 {{{ 22 $ rasql -q "select oid(t) from MOD_WATERVAPOR_32633_1000 as t" --out 23 string 24 rasql: rasdaman query tool v1.0, rasdaman v8 -- generated on 25 31.01.2012 17:14:19. 26 opening database RASBASE at localhost:7001...ok 27 Executing retrieval query...ok 28 Query result collection has 1 element(s): 29 Result element 1: 213505 30 rasql done. 31 }}} 32 It would appear to be an issue only for the oid() operator and 33 '''displayed output''' since a different query based on oid works as 34 expected: 35 {{{ 36 rasql -q "select csv(m[0:10,0:10]) from mr as m where oid(m)=31745" -- 37 out string 38 }}} 39 But in the meantime anything relying on getting oids with select 40 breaks. 5 in `reladminif/oidif.hh` to long, and accordingly update the code that depends on it (which doesn't seem that much).