PlaceTable rows with PlaceType=0 and MasterID != 0
I was just checking referential integrity in my database and I noticed a significant number of rows (~250 out of 7500 rows) in the PlaceTable that have PlaceType = 0 but MasterID is non zero.
Do the non zero MasterIDs have any significance for PlaceType=0 rows, or are they just the result of previous bugs?
I don't see a pattern.
Background- It's my understanding that PlaceType =0 indicates a primary place while PlaceType=2 indicates a place detail with its MasterID pointing to a primary place.
Richard
Your understanding is correct and the MasterID is ignored by RM when PlaceType=0, afaik. In my scripts at Places – Conversion of Place Details to Places, the MasterID is prefixed by * when the PlaceType is updated from 2 to 0 by the convert script so that the revert script can do its job when run.
I'm unaware of what operation in RM might have left Place records with non-zero MasterIDs. Does Place Cleanup have a combine function?
Hmm interesting that is about 10% of rows (913)
I wonder if Spliting etc in RM UI might do that --I have a lot with 1600 Master ID let me do another query
Uploaded files:
here is a rank break down
Uploaded files:
An issue I ran across last year was the Place Details UI was using a 16 bit integer, so updating or merging place details would result in any PlaceId > 32768 would display but changing it would corrupt that place entry as the sign bit would be truncated. This would result in masterids > 0 for placetype = 0
I see a large number of masterids with 16777219 which is 0b1000000000000000000000011 which is a poorly translated sign bit error.