Opened 11 years ago
Closed 10 years ago
#775 closed defect (fixed)
Add primary keys to petascopedb tables where not defined
Reported by: | damiano | Owned by: | Piero Campalani |
---|---|---|---|
Priority: | major | Milestone: | 9.0.x |
Component: | petascope | Version: | 9.0 |
Keywords: | primary keys | Cc: | mantovani |
Complexity: | Easy |
Description (last modified by )
In petascopedb version 9
Eg. Table ps_vector_coefficients has no primary key.
Change History (6)
comment:1 by , 10 years ago
Milestone: | → 9.0.x |
---|
comment:2 by , 10 years ago
Description: | modified (diff) |
---|---|
Keywords: | primary keys added |
Status: | new → accepted |
Summary: | Primary key in ps_vector_coefficients TABLE → Add primary keys petascopedb where not defined |
comment:3 by , 10 years ago
Summary: | Add primary keys petascopedb where not defined → Add primary keys to petascopedb tables where not defined |
---|
comment:4 by , 10 years ago
comment:5 by , 10 years ago
Fixed in changeset:ff965c7 : for those two tables, (logically) equivalent UNIQUE constraints where set instead of PK constraints (now all tables have a PK index).
Damiano let me know if I can close this one, thanks.
comment:6 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
I think we can obviously close it
Note:
See TracTickets
for help on using tickets.
So far no PK found in
ps_vector_coefficients
(WCS) andps_servicelayer
(old WMS schema).