On Fri, 2006-01-27 at 13:01, Charles Baker wrote: > That's disheartening :-( My goal is to upgrade my old mysql installation > to the point where I can import the roller data into a new database > created with the roller 2.0 createdb.sql script.
yes. the problem is that we didn't have a clearly defined upgrade process before 1.3, so by far the best solution is just to deploy each release individually until you get to 1.3. from 1.3 onward you should be able to skip releases. > > It seemed like I had things working somewhat. In that the main page > showed my old posts. But then I ran into the user can't login problem > that I saw discussed, but never saw solved. > > BTW, is it customary here to post replies at the top or bottom of the > old message? no standard, but I'll say that I prefer the top. -- Allen > > > > -----Original Message----- > > From: John Greenhill [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 27, 2006 3:31 PM > > To: [email protected] > > Subject: RE: 110-120-migration.sql > > > > I put a lot of time in upgrading from 098 to 130 and ran into a number > of > > issues you're finding. I got the same errors on the scripts, but since > it > > was just for some constraints I continued the process to see how it > would > > go. > > > > I found that the scripts alone were not sufficient to jump versions, > but > > that different roller versions actually had database modifications > coded > > into the java. Thus, I had to write my own scripts to do what the java > in > > each version did (things like adding an admin user, dealing with > > categories > > and associations etc). > > > > I never did go back and fix the constraint thing, so I'll be > interested in > > what you find. > > > > -John > > > > -----Original Message----- > > From: Charles Baker [mailto:[EMAIL PROTECTED] > > Sent: Friday, January 27, 2006 10:52 AM > > To: [email protected] > > Subject: 110-120-migration.sql > > > > This script ran fine until it got to the end where some foreign keys > are > > being created > > > > alter table pingtarget add constraint pingtarget_websiteid_fk > > foreign key (websiteid) references website(id); > > > > alter table autoping add constraint autoping_websiteid_fk > > foreign key (websiteid) references website(id); > > > > alter table autoping add constraint autoping_pingtargetid_fk > > foreign key (pingtargetid) references pingtarget(id); > > > > alter table pingcategory add constraint pingcategory_autopingid_fk > > foreign key (autopingid) references autoping(id); > > > > alter table pingcategory add constraint pingcategory_categoryid_fk > > foreign key (categoryid) references weblogcategory(id); > > > > I get error 1005 from mysql. Google yielded a tip that an index should > > be on the field before trying to create the foreign key. Using the > first > > alter table statement as an example, would that mean that an index > needs > > to be created on website(id)?
