Describe the bug

The response of MongoDB is inconsistent wrt to SQL databases if the schema has links of type array. When the nested table doesn't have any rows/documents in it. The response returned is different

Expected behaviour

Actual behaviour

Steps to reproduce

• Fire the query & observer the result

link table as array
if nested table has no rows, postgres 

Location

• Browser
• CLI
• API
• Documentation

Motivation

Connecting to AWS RDS is complicated without a step-by-step guide unique to Porter.

Requirements

• Document how to set up the RDS instance if it doesn't exist.
• Document how to connect to the RDS instance from the same VPC.
• Document how to configure VPC peering if an RDS instance already exist

$ minishift status
Minishift:  Running
Profile:    minishift
OpenShift:  Stopped
DiskUsage:  ERR of

perhaps this is related to the error state from the OpenShift isRunning check

The background is in #1786 .

We should allow revision created by outside system. So we should add a mechanism to check if the revision already exist.

The quick solution could be:

1. calculate the revision hash
2. list all revision related(label selector app name)
3. check if there's existing revision with same hash and compare the spec. If they are deep equal, don't generate.

_Origin

1、当没有API文档时的空数据提示
2、当没有搜索到API文档时的空数据提示