Re: Test changing the backend / export - import
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Nov 03, 2021 at 07:01:16AM +0000, SCHLEMMER Norbert wrote: > Hello > Last weekend I tested the "TurnKey-Linux Roundup Appliance". Got the > application up and running under Hyper-V but the roundup import > failed. > The export was done with Roundup 2.1.0 and SQLite DB under Windows > Server 2019. > > https://www.turnkeylinux.org/comment/50396#comment-50396 > > Jeremy Davis pointed me to > https://issues.roundup-tracker.org/issue2550815 : roundup-admin import for postgres causes id to be skipped > > The TurnKey Appliance is backed by MySQL/MariaDB and it seems to be > the same cause. > > Any idea how to move from SQLite DB backend to MySQL/MariaDB or PostgreSQL ? What error are you getting? The issue in question is still unfixed but will *not* have the effect that the resulting mysql or postgresql backend database is unusable or the import fails. So if you're getting problems during the import we'd like to know the errors you get. The mentioned issue has the following effect on export/import: - When you export you might have issue ID numbers 1-100 - You export and re-import into a different tracker - The next issue you create in the new tracker will have ID 102 not 101 We consider this a benign problem. There are other cases where issue-numbers can be skipped such as when you're creating an issue and an auditor makes the creation fail. In that case the next successful creation will have skipped an ID number, too. You should not rely on ID numbers being dense. Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: www.runtux.com Reichergasse 131, A-3411 Weidling email: [email protected]