Dataset Record 500 when should be 400: add aliasqueryaref

[aurreco-uga]

(found URL in error emails)
check teh difference between:
https://microbiomedb.org/mbio/app/record/dataset/DS_1c4b2eeecb
and
https://microbiomedb.org/mbio/app/record/dataset/bbbbbbbb

[ryanrdoherty]

This has nothing to do with the client. The issue is similar to what we've seen recently with alias queries. In mbio, the alias query for datasets is:

        <sql includeProjects="ClinEpiDB,MicrobiomeDB">
        <![CDATA[
                  select dataset_presenter_id as dataset_id,
                         dataset_presenter_id as old_dataset_id
                  from apidbTuning.DatasetPresenter
                    UNION
          SELECT d.dataset_stable_id, d.dataset_stable_id
          FROM apidbuserdatasets.installeduserdataset i, 
               apidbuserdatasets.datasetattributes d
          WHERE i.user_dataset_id = d.user_dataset_id
        ]]>
        </sql>

This SQL returns a row for DS_1c4b2eeecb, indicating that it is a real ID, but not for bbbbbbbb, so bbbbbbbb throws 404. Then when we try to join DS_1c4b2eeecb to the attribute query, DatasetAttributes.ClinepiStudyAttributes, there's no data so we get 500. Makes sense to me that a table named ClinepiStudyAttributes would not have data for an mbio study.

[aurreco-uga]

we need the aliasqueryref..

[ryanrdoherty]

@aurreco-uga No, that's not what I was saying. Not sure why mbio datasets are trying to join to DatasetAttributes.ClinepiStudyAttributes, but that is the problem.