Custom Query (2765 matches)

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

The rasdaman configuration are defined in different places and using different styles and it is very difficult to trace these configurations. For examples, the globals.hh file define many external variables that control the behavior of rasdaman. Another place of configuration is rasmgr.conf. In these two places one can observe that there are redundancy in the definitions. Another place where one can find general definitions of configuration is inline the source code. for example rasql.cc repeats the same definition in glabals.hh and rasmgr.conf

Please see below

rasql.cc #define PARAM_SERV_FLAG 's' #define PARAM_SERV "server" #define HELP_SERV "<host-name> rasdaman server" #define DEFAULT_SERV "localhost"

#define PARAM_PORT_FLAG 'p' #define PARAM_PORT "port" #define HELP_PORT "<p> rasmgr port number" #define DEFAULT_PORT 7001 #define DEFAULT_PORT_STR "7001"

….

const char *serverName = DEFAULT_SERV; r_ULong serverPort = DEFAULT_PORT; const char *baseName = DEFAULT_DB; const char *user = DEFAULT_USER; const char *passwd = DEFAULT_PASSWD;

glabals.hh

/ default rasmgr listen port #define DEFAULT_PORT 7001

/ name of env var pointing to rasdaman home dir (ex: "/opt/rasdaman") #define RMANHOME_VAR "RMANHOME"

/ default name of server machine, if gethostname() fails #define DEFAULT_HOSTNAME "localhost"

/ default database name #define DEFAULT_DBNAME "RASBASE" ……

rasmgr.conf

define db RASBASE -dbh rasdaman_host

# define a rasdaman database server process with name N1 # parameters: # -host h name of the host machine the server runs on # (cf: man 1 hostname) # -type t communication protocol type is t # (one of: 'r' for RPC, 'h' for HTTP, 'n' for RNP); # recommended: use 'n', all others are deprecated # -port p port number for contacting this server is p # (rasmgr by default uses 7001, so you may simply count up) # -dbh d use database host d (see "define dbh" for allowed names

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.