Re: export / import errors from postgresql to mysql
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jun 24, 2014 at 08:58:09AM -0500, Chad Seys wrote: > Hi Ralf! > > Are you sure you copied the schema.py used in the *old* tracker to the > > new one *before* calling import? > > Ah! no, not schema.py, just config.ini . Let me give that a try! :) b/c I > have hope! > > If this imports successfully, should I run roundup-admin migrate? Not necessary but doesn't hurt. You're using the same roundup version for both, the export DB and the import DB? The migrate step should be done when you're upgrading to a later roundup version. > Can I then update the schema.py to the current version? > > (What order should I do things in?) First do the conversion with the old schema.py, then if you want to add/remove fields in the new database you can change the schema *after* the conversion. As you already experienced, a database export depends on the schema used to export it, so it can only be imported into the same schema (not quite true, it must be a subset of the new schema but you're on the safe side if you keep it the same). Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: http://www.runtux.com Reichergasse 131, A-3411 Weidling email: [email protected] allmenda.com member email: [email protected] ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft