why not just use the dump feature in sqlite/mysql/pgsql all dbs have a 'dump' function/app that exports the contents to a generic format that can be read/altered to be read by another db
going to pgsql you might have to run it through a filtering app, but mysql is pretty lax (just test your data to make sure its all there. probably best to run in 'traditional sql' mode if you have 5.0 ) > I need to bear in mind here that when I put the data back in (with a > simple script) some of the class names or field names might have > changed, so I will need another nested dictionary (?) of changes that > will override the other dictionary. Thats a nightmare. backup your db on box 1, coerce your data into the new schema, and export to ascii with a dump utility. (when i do stuff like that, i keep a log of all the necessary sql commands) making filters to change data will just be a nightmare. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
