Zhihang Yao issues

Results 43 issues of


                                            Zhihang Yao

drop the "relation_id" column from the property table

This ist a deprecated column, since the `feature_relation` table dosn't exist anymore

Drop the UNIQUE constraint on the gmlid column

We want to use the `feature` table to store mulitple versions of the same city objects, and the `gmlid` column values may not always keep UNIQUE. The UNIQUE constraint must...

The "address" table needs to be back

We note that it would be more efficient/easier for performing address queries, if the complex xalAddress data are mapped onto a separate table `address` like in the current 3DCityDB v4.

Add new column "lod" in property table

We'll add a new column `lod` to the property table for facilitating e.g. lod filter export. The first proposal for alpha release is to use string type to store any...

Rename the "mimetype" column to "mime_type" in the codelist table

A tiny change to make the naming consistent like in the table `implicit_geometry` and `tex_image`

Drop or update the UNIQUE constraint "property_unique_feature_id_namespace_name_index"

The following UNIQUE constraint is defined in the current `property` table: ``` CONSTRAINT property_unique_feature_id_namespace_name_index UNIQUE ( feature_id, namespace, name, index_number ) ``` How about the following case, where the unique...

Consistent property FK column naming convention

Most FK columns (e.g. `val_grid_coverage`, `val_appearance`, `val_dynamizer`) follows the naming convention "val_[referencedTable]". An exception is `val_implicitgeom_id`. We should make it consistent by renaming this column to `val_implicitgeom` or add the...

Zhihang Yao