Re: [Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
Yes. That's true. I've never had to make a jump that big and I've only read on this forum that that is how the problem was solved. You could jump into a debugger and find out what's happening, but it's probably easier and faster to try the gems first. But please report the bug if you do find it! On Fri, Aug 31, 2012 at 11:37 AM, Peterdk wrote: > Ok, > > I'll try that. But I am a bit wondering why that would help? The database is > only edited int the migrations process, isn't it? > Aren't these just cumulatively added during new releases? > > Peter > > Op vrijdag 31 augustus 2012 16:35:42 UTC+2 schreef Jim Gay het volgende: >> >> That's what I mean. >> I wanted to make sure you didn't have it misconfigured so we could >> rule that out. >> >> I recall in years past that others would have success in stepping up >> their installation. >> You might get it to work by going a version or 2 up before getting to 1.1. >> >> Can you try going to 0.7.2 first or 0.8.2? >> >> On Fri, Aug 31, 2012 at 10:29 AM, Peterdk wrote: >> > What do you mean? >> > The development database config is just the standard slite db, that I >> > don't >> > use. >> > I have the production database configured to be mysql, just as on my old >> > host. I only changed the database name, when imported the old dump into >> > the >> > new mysql server. >> > I do run rake with "production db:migrate". >> > >> > Op donderdag 30 augustus 2012 19:32:50 UTC+2 schreef Jim Gay het >> > volgende: >> >> >> >> Are you running these in the correct environment? >> >> For example you're running "rake production db:migrate" but is your >> >> existing database setup for the development configuration? >> >> >> >> On Thu, Aug 30, 2012 at 1:03 PM, Peterdk wrote: >> >> > Hi, >> >> > >> >> > I am running a website on a old host that is going to shutdown, and >> >> > so I >> >> > am >> >> > in the process of moving it to my vps. >> >> > It's still runing on radiant 0.6.4. >> >> > >> >> > I tried to update to the current radiant gem (1.0.1), and then tried >> >> > migrating: >> >> > I updated the project according to the 0.6 upgrade instructions: >> >> > However, when I come to the point of migrating the database, I have a >> >> > problem: >> >> > rake production db:migrate runs without errors, but the end result is >> >> > a >> >> > database with empty tables. All data is gone. >> >> > Is there anything I can do to get this to upgrade? The old radiant >> >> > 0.6.4 >> >> > doesn't work on this host, it looks like it doesn't like my ruby >> >> > 1.9.3 >> >> > >> >> > Peter >> >> >> >> >> >> >> >> -- >> >> Write intention revealing code #=> http://www.clean-ruby.com >> >> >> >> Jim Gay >> >> Saturn Flyer LLC >> >> 571-403-0338 >> >> >> >> -- >> Write intention revealing code #=> http://www.clean-ruby.com >> >> Jim Gay >> Saturn Flyer LLC >> 571-403-0338 -- Write intention revealing code #=> http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
Re: [Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
Ok, I'll try that. But I am a bit wondering why that would help? The database is only edited int the migrations process, isn't it? Aren't these just cumulatively added during new releases? Peter Op vrijdag 31 augustus 2012 16:35:42 UTC+2 schreef Jim Gay het volgende: > > That's what I mean. > I wanted to make sure you didn't have it misconfigured so we could > rule that out. > > I recall in years past that others would have success in stepping up > their installation. > You might get it to work by going a version or 2 up before getting to 1.1. > > Can you try going to 0.7.2 first or 0.8.2? > > On Fri, Aug 31, 2012 at 10:29 AM, Peterdk > > wrote: > > What do you mean? > > The development database config is just the standard slite db, that I > don't > > use. > > I have the production database configured to be mysql, just as on my old > > host. I only changed the database name, when imported the old dump into > the > > new mysql server. > > I do run rake with "production db:migrate". > > > > Op donderdag 30 augustus 2012 19:32:50 UTC+2 schreef Jim Gay het > volgende: > >> > >> Are you running these in the correct environment? > >> For example you're running "rake production db:migrate" but is your > >> existing database setup for the development configuration? > >> > >> On Thu, Aug 30, 2012 at 1:03 PM, Peterdk wrote: > >> > Hi, > >> > > >> > I am running a website on a old host that is going to shutdown, and > so I > >> > am > >> > in the process of moving it to my vps. > >> > It's still runing on radiant 0.6.4. > >> > > >> > I tried to update to the current radiant gem (1.0.1), and then tried > >> > migrating: > >> > I updated the project according to the 0.6 upgrade instructions: > >> > However, when I come to the point of migrating the database, I have a > >> > problem: > >> > rake production db:migrate runs without errors, but the end result is > a > >> > database with empty tables. All data is gone. > >> > Is there anything I can do to get this to upgrade? The old radiant > 0.6.4 > >> > doesn't work on this host, it looks like it doesn't like my ruby > 1.9.3 > >> > > >> > Peter > >> > >> > >> > >> -- > >> Write intention revealing code #=> http://www.clean-ruby.com > >> > >> Jim Gay > >> Saturn Flyer LLC > >> 571-403-0338 > > > > -- > Write intention revealing code #=> http://www.clean-ruby.com > > Jim Gay > Saturn Flyer LLC > 571-403-0338 >
Re: [Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
That's what I mean. I wanted to make sure you didn't have it misconfigured so we could rule that out. I recall in years past that others would have success in stepping up their installation. You might get it to work by going a version or 2 up before getting to 1.1. Can you try going to 0.7.2 first or 0.8.2? On Fri, Aug 31, 2012 at 10:29 AM, Peterdk wrote: > What do you mean? > The development database config is just the standard slite db, that I don't > use. > I have the production database configured to be mysql, just as on my old > host. I only changed the database name, when imported the old dump into the > new mysql server. > I do run rake with "production db:migrate". > > Op donderdag 30 augustus 2012 19:32:50 UTC+2 schreef Jim Gay het volgende: >> >> Are you running these in the correct environment? >> For example you're running "rake production db:migrate" but is your >> existing database setup for the development configuration? >> >> On Thu, Aug 30, 2012 at 1:03 PM, Peterdk wrote: >> > Hi, >> > >> > I am running a website on a old host that is going to shutdown, and so I >> > am >> > in the process of moving it to my vps. >> > It's still runing on radiant 0.6.4. >> > >> > I tried to update to the current radiant gem (1.0.1), and then tried >> > migrating: >> > I updated the project according to the 0.6 upgrade instructions: >> > However, when I come to the point of migrating the database, I have a >> > problem: >> > rake production db:migrate runs without errors, but the end result is a >> > database with empty tables. All data is gone. >> > Is there anything I can do to get this to upgrade? The old radiant 0.6.4 >> > doesn't work on this host, it looks like it doesn't like my ruby 1.9.3 >> > >> > Peter >> >> >> >> -- >> Write intention revealing code #=> http://www.clean-ruby.com >> >> Jim Gay >> Saturn Flyer LLC >> 571-403-0338 -- Write intention revealing code #=> http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
Re: [Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
What do you mean? The development database config is just the standard slite db, that I don't use. I have the production database configured to be mysql, just as on my old host. I only changed the database name, when imported the old dump into the new mysql server. I do run rake with "production db:migrate". Op donderdag 30 augustus 2012 19:32:50 UTC+2 schreef Jim Gay het volgende: > > Are you running these in the correct environment? > For example you're running "rake production db:migrate" but is your > existing database setup for the development configuration? > > On Thu, Aug 30, 2012 at 1:03 PM, Peterdk > > wrote: > > Hi, > > > > I am running a website on a old host that is going to shutdown, and so I > am > > in the process of moving it to my vps. > > It's still runing on radiant 0.6.4. > > > > I tried to update to the current radiant gem (1.0.1), and then tried > > migrating: > > I updated the project according to the 0.6 upgrade instructions: > > However, when I come to the point of migrating the database, I have a > > problem: > > rake production db:migrate runs without errors, but the end result is a > > database with empty tables. All data is gone. > > Is there anything I can do to get this to upgrade? The old radiant 0.6.4 > > doesn't work on this host, it looks like it doesn't like my ruby 1.9.3 > > > > Peter > > > > -- > Write intention revealing code #=> http://www.clean-ruby.com > > Jim Gay > Saturn Flyer LLC > 571-403-0338 >
Re: [Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
Are you running these in the correct environment? For example you're running "rake production db:migrate" but is your existing database setup for the development configuration? On Thu, Aug 30, 2012 at 1:03 PM, Peterdk wrote: > Hi, > > I am running a website on a old host that is going to shutdown, and so I am > in the process of moving it to my vps. > It's still runing on radiant 0.6.4. > > I tried to update to the current radiant gem (1.0.1), and then tried > migrating: > I updated the project according to the 0.6 upgrade instructions: > However, when I come to the point of migrating the database, I have a > problem: > rake production db:migrate runs without errors, but the end result is a > database with empty tables. All data is gone. > Is there anything I can do to get this to upgrade? The old radiant 0.6.4 > doesn't work on this host, it looks like it doesn't like my ruby 1.9.3 > > Peter -- Write intention revealing code #=> http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338
[Radiant] Migrating from 0.6.4 to current 1.0.1 results in empty database
Hi, I am running a website on a old host that is going to shutdown, and so I am in the process of moving it to my vps. It's still runing on radiant 0.6.4. I tried to update to the current radiant gem (1.0.1), and then tried migrating: I updated the project according to the 0.6 upgrade instructions: However, when I come to the point of migrating the database, I have a problem: rake production db:migrate runs without errors, but the end result is a database with empty tables. All data is gone. Is there anything I can do to get this to upgrade? The old radiant 0.6.4 doesn't work on this host, it looks like it doesn't like my ruby 1.9.3 Peter
