Opened 7 years ago

Closed 3 years ago

#53 closed enhancement (fixed)

Processing marray objects not in the database

Reported by: m.owonibi@… Owned by: dmisev
Priority: major Milestone: Future
Component: applications Version: 8.3
Keywords: Cc: pbaumann
Complexity: Very Hard

Description

rasdaman should be improved to be able to use marray objects which are not necessarily in the database in its query processing. Those marray objects are usually passed using the $1 symbol.
For example:
select jpeg(inv_tiff($1) + r) from mr as r' --file anything.tif

Currently, the $1 symbol is only used when data is to be inserted, however, i will like to use it in the select statement.
Using the $1 symbol in insert statement currently returns this error.

rasdaman:~$ rasql -q 'select inv_jpeg($1) + r from rgb as r' --file rasql_1.jpeg
rasql: rasdaman query tool v1.0, rasdaman v8 -- generated on 27.07.2010 09:46:21.
opening database RASBASE at localhost:7001...ok
fetching type information for GreyString? from database, using readonly transaction...ok
reading file rasql_1.jpeg...ok

constant 1: GMarray
Oid...................:
Type Structure........:
Type Schema...........: marray< char >
Domain................: [0:19834]
Base Type Schema......: char
Base Type Length......: 1
Data format.......... : Array
Data size (bytes).... : 19835

Executing retrieval query...rasdaman error 373: Execution error 373 in line 1, column 17, near token #MDD0#: Unsatisfied MDD constant parameter.
aborting transaction...ok
rasql done.

Furthermore, it will be appropriate if rasdaman can handle several of these marray objects which are not in the database in a query processing e.g
rasql -q 'select inv_jpeg($1) + inv_tiff($2) + r from rgb as r' --file jpegimage.jpeg tiffimage.tiff

Change History (4)

comment:1 Changed 6 years ago by dmisev

  • Cc pbaumann added
  • Owner set to dmisev
  • Status changed from new to accepted

comment:2 Changed 4 years ago by pbaumann

  • Milestone set to 9.0
  • Version set to 8.3

comment:3 Changed 3 years ago by dmisev

  • Complexity set to Very Hard
  • Milestone changed from 9.0.x to Future

comment:4 Changed 3 years ago by dmisev

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.