(Gemini v2.0.3) - Correct project id reported on issue table, but incorrectedly reported on issuehis
I am looking at my production gemini database and seeing the following problem which i think is the "show stopper" error for my upgrade (stuck at step1 script) to Gemini V3.0.4
Production database (v2.0.3)
Issue table, issueid = 3267, projid=11 (this is valid projid)
Issuehistory table, issueid=3267, projid=-1 (very invalid projid)
Question: I don't know how -1 appears on issuehistory table while the same issueid appears on Issue table with correct/valid (but different) projid. Can anyone tell me how this -1 error appear? I know user cannot do this on the Gemini website. Also, I don't believe any admin created this -1 on the database.
kha
· 1 |
|
Monday, December 1, 2008, 9:13:04 PM |