Downgrade 4.0 database to 3.0 database
Turning a 4.0 database into a 3.0 database means deleting a few columns from the 4.0 database and changing the version stamp.
Delete these columns:
- Area: nType, cDoc
- Bug: ixBugEventLatest, fTrained, fReplied, fForwarded, ixOriginalPrediction, nStatType, sTicket, sReleaseNotes, ixDiscussTopic, dtDue
- BugEvent: ixAttachment
- Filter: ixGroup, sComputer, sVersion, dueInNext, fGlobal
- Mailbox: fDeleted, fAutoSort, fAutoReply, sReplySubject, sReplyMessage, fDueDate, nDue, nDueTime, sLastMessageDownloaded
- Person: fEscalationReport, fGridView, FILTER_sComputer, FILTER_sVersion, FILTER_dueInNext, FILTER_ixGroup, sSnippetKey, viewCol1, viewCol2, viewCol3, viewCol4, viewCol5, viewCol6, viewCol7, FILTER_sFilterName
- Project: ixGroup, fInbox
Add these columns:
- Filter: fGridView int NULL
- Person: FILTER_fGridView int NULL
Delete these tables completely:
- ACL
- Attachment
- AutoResponseRecord
- BugRelation
- DBUpdate
- DiscussEmail
- DiscussGroup
- DiscussLayout
- DiscussTopic
- Groups
- Holiday
- MailQueue
- Notification
- Prediction
- Snippet
- SorterSetting
- SorterToken
- TokenAssociation
- TrainingRequest
- WorkingSchedule
Change the ixVersion value in the Version table to the number 328.
Note: Attachments uploaded to a 4.0 database will not be available once the database is downgraded to 3.0. There is no workaround for this.
