Composite type creation over old types.

[Ernesto Rodriguez]

Defining a composite type (such as an array or set) over an existing in the database failes since the parser dosen't check for the items in the database. In other words, a type that appears in definition file 1 cannot be used in definition file 2. The attached files provide more details. This is a defect of the rasdl component of rasdaman.

[Ernesto Rodriguez]

Type definition files where types2.dl depends on types.dl

[beccati@…]

I can confirm this issue, moreover it is not possible to redefine the type either because the component complains about struct type name already existing if you replicate the definition in the second file:

rasdl: rasdaman schema and database manipulation tool, rasdaman v8.3 on base DBMS pgsql — generated on 22.02.2012 12:30:51.
Reading rasdaman data definition file ModP20Types-tmp.dl…inserting symbols into database…EDL003 rasdaman error: 905: Evaluation error 905 in line 1, column 1, near token ModP20Pixel: Struct type name exists already.
rasdl done.

[Dimitar Misev]

Actually this should be marked as an enhancement. Struct types are not typedefs, they do not define a new type in the database, so existing ones cannot be referenced in new type definitions.

[Peter Baumann]

is this still pending, or can it be closed?

[Dimitar Misev]

The new implementation by George supports this, rasdl not. So depends on whether we plan on fixing it in rasdl (I'd vote we close it).

[Dimitar Misev]

We declare rasdl deprecated, so let's close.