![]() Write out a flat file containing topic/post/post data/user info that we do want to migrate.I can generate that flat file from msql just as easily. I need a flat file to run through a program on the server. Have the conversion program filter on which posts it migrates.Īfter doing this analysis, I realize I don’t need the data in postgres at all. Some forums aren’t appropriate to migrate (off topic, jforum team relax, test forum) Have the conversion program ignore the source data forum and choose our JForum forum id. The topics come from multiple forums in the source data and we want them to end up in the same forum. The original user can be specified in the post as a footer. Have all posts show as being from the same “Migrated from jforum” user. The user ids of the source data are already in use by our forum and some of the members duplicate. The topic/post id numbers the source data uses are already in use by our forum. Read the source data into a new file format and then use the java JForum API to create the topics/posts for consistency with our schema changes. ![]() We’ve added columns to two of the tables. I’m listing the significant ones here along with my approach for handling. While we have a one to one mapping with the table names, we have a number of adjustments that need to be made. There are just under 5000 topics and 20,000 posts. It was really fast The 34 meg import took less than 30 seconds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |