yes, that is correct. i'm not sure what happened with the script generation though.
-- Allen On Fri, 2006-01-27 at 10:12, Charles Baker wrote: > Closer reading leads me to believe that BOOLEAN_SQL_TYPE should be > replaced with 'bit'. Is this correct? Was this supposed to be a velocity > substitution? This thread of discussion led me to this conclusion: > > http://sourceforge.net/mailarchive/forum.php?thread_id=5518761&forum_id= > 9297 > > > ---- > Charles H. Baker > O: 864.422.5349 C: 864.201.8456 > [EMAIL PROTECTED] > There's nothing wrong with getting a steady paycheck, unless it > interferes with your ability to earn what you're worth. There's the rub. > It usually does. -- T Harv Eker > > -----Original Message----- > From: Charles Baker [mailto:[EMAIL PROTECTED] > Sent: Friday, January 27, 2006 12:57 PM > To: [email protected] > Subject: RE: import 0.9.8.2 roller data to roller 2.0 > > Allen, thanks for you help so far. I've got some downtime from other > responsibilities and I'm back at this. > > I was wrong about my mysql installation, it was 4.0.20a. So, I upgraded > it to 4.1.16. My roller install is 0.9.8.2. That version of roller is > working with my upgraded mysql. However, when I attempt to run the file > named 098-to-099-migration.sql, I get this error: > > 1064- You have an error in your SQL syntax; check the manual that > corresponds to your MYSQL server version for the right syntax to use > near 'BOOLEAN_SQL_TYPE not null)' at line 1. > > Some googling for that only points to a few things on roller, but not a > solution that I can see. > > ---- > Charles H. Baker > O: 864.422.5349 C: 864.201.8456 > [EMAIL PROTECTED] > There's nothing wrong with getting a steady paycheck, unless it > interferes with your ability to earn what you're worth. There's the rub. > It usually does. -- T Harv Eker > > -----Original Message----- > From: Allen Gilliland [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 12, 2006 4:02 PM > To: [email protected] > Subject: Re: import 0.9.8.2 roller data to roller 2.0 > > I would highly suggest that you upgrade one version at a time since your > database is so old. That is the only way that things are pretty much > guaranteed to work (knock on wood). > > It would definitely help to do the db switch separately as well. I > would recommend doing the upgrade against the 4.1.x db and get Roller > 2.0 working with that, then try to migrate the data to mysql 5.x. > > -- Allen > > > On Thu, 2006-01-12 at 12:58, Charles Baker wrote: > > I've successfully imported data from all the 0.9.8.2 tables to 2.0 > > tables except for the weblogentry, webpage and website tables. It > > appears that the structure of these tables is too different for a > > straight data dump and restore. To further complicate matters, the old > > db is mysql 4.1.x and the new db is mysql 5.x. For example, below is > the > > log of my attempted import of webpage. If I change the indicated error > > (Incorrect datetime value: 'ing:-pa-dd 5') to a proper date, I get > > constraint related errors. Has anyone successfully made this leap? > > Should I upgrade mysql first, then run those various upgrade scripts > > that are supplied with roller? > > >
