Custom Query (2765 matches)

Currently, int division yields int, which sometimes is not what is expected. This may have significant impact on operation results. Of course, this can be overcome by casting operands to float, but this may not be intuitive to all QL users. We need to investigate whether the division result type should always be a float or double.

The example files provided with Rasdaman do not execute properly on Ubuntu 32-bit. Below I provide sample output.

$ ./avg-cell localhost 7001 RASBASE rgb rasguest rasguest

Opening database RASBASE on localhost... OK
Starting read-only transaction ... OK
Looking up collection rgb ...OK
Collection contains 1 entries
Exception: Ref Null

$ ./lookup localhost 7001 RASBASE rgb rasguest rasguest

Opening database RASBASE on localhost... OK
Starting read-only transaction ... OK
Looking up collection rgb ...OK
Collection
  oid...................: PostgreSQL|RASBASE|1538
  type name.............: rgb
  type structure........: set <marray <struct { char red, char green, char blue }, 2>>
  type schema...........: set< marray< struct{ char red, char green, char blue } > >
  number of entries.....: 1
  Element type schema...: marray< struct{ char red, char green, char blue } >

Image 1
Exception: Ref Null

$ ./query localhost 7001 RASBASE rgb rasguest rasguest

Opening database RASBASE on localhost... OK
Starting read-only transaction ... OK
Creating the query object ...OK, Query string is: 
            select a$1 from $2 as a where some_cells( a$3 > $4 )
Substituting query parameters ...OK, Query string is: 
            select a[0:4,0:4] from rgb as a where some_cells( a[8:9,8:9] > 10 )
Executing the query ...FAILED
(no explanation text available - cannot find/load file with standard error messages.)
Aborting transaction ... OK
Closing database ... OK

Changing rasmgr configuration file does not affect the rasdaman connection string. For example, I changed the following line of rasmgr,conf

define dbh rasdaman_host -connect RASBASE

to define dbh rasdaman_host -connect RASBASE@Elocalhost

and by tracing the the globalConnectId variable it seems that changing the configuration file did not affect it since its value in both cases is the same.