
dougthompson
User
Nov 9, 2006, 7:21 AM
Post #4 of 10
(1374 views)
Shortcut
|
|
Re: [Dave] SQL migration problem
[In reply to]
|
Can't Post
|
|
Dave: Thanks for the feedback. We had a number of archives in our old flat-file database under 1.41. When we upgraded to 2.0 it coverted the archives back to active database entries but the archive field and archive number remained part of the new flatfile database. After several failures and hangups on the archive data field, I eliminated that field from the flatfile and it started importing the articles. Then we got the same error when it tried to import the catefory db table. We had 37 categories (including seven with no data in them) so I trimmed the fields down to 30 and tried again. Same result. When I get a chance, I'm going to go through each category listing and look for data problems. If that doesn't work, I'll fill out a support form. First I want to see if I can work it out here. I'm hoping we can get it sorted out because we may have to abandon AM if it doesn't work. Our database is far too big to work as a flatfile. As I noted in another post, we also use Movable Type for our onsite blog and I've been using it for news stories as well since we ran into the conversion problem with AM. We have more than 10,000 articles and 50,000 comments running in the MT MySQL database without a hitch. We just updated to MT's Enterprise edition and it is both fast and stable. I still prefer the AM interface and its features but I need the speed of a database interface. Doug
|