Petascope - "type already exists" error message when RASBASE is cleaned up but not petascope

[Bang Pham Huu]

This happens when petascopedb has imported data, but RASBASE is blank.
Then, one wants to update an existing coverage.

Petascope cannot find the rasdaman types of this coverage and it will throw exception "type already exists".

It should throw better error message, like "collection does not exist to update".

[Bang Pham Huu]

I did a test with a coverage exists in petascopedb, RASBASE is cleaned, and then run wcst_import to update this existing coverage.

Petascope throws proper error from rasdaman: collection name does not exist.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ows:ExceptionReport version="2.0.1"
    xsi:schemaLocation="http://www.opengis.net/ows/2.0 http://schemas.opengis.net/ows/2.0/owsExceptionReport.xsd"
    xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">
    <ows:Exception exceptionCode="CollectionDoesNotExist">
        <ows:ExceptionText>Error: collection name does not exist</ows:ExceptionText>
    </ows:Exception>
    <ows:Exception exceptionCode="CollectionDoesNotExist">
        <ows:ExceptionText>UPDATE test_rgb SET test_rgb[0:399,0:343] ASSIGN decode(<[0:0] 1c>, "GDAL", "{\"variables\":[0,1,2],\"filePaths\":[\"/home/rasdaman/rasdaman_community/rasdaman/systemtest/testcases_services/test_all_wcst_import/testdata/wcps_rgb//rgb.png\"]}")</ows:ExceptionText>
    </ows:Exception>
</ows:ExceptionReport>