Re: Changing Property Types

[Oren Eini]

You should be able to just do the change. And every time that you
load / save a Part, it will update the value from int to string.
There shouldn't be anything else that you need to do.

On Nov 16, 7:07 pm, EisenbergEffect <r...@bluespireconsulting.com>
wrote:
> I have some data in production that is being stored as an int. I need to
> change the property type to a string. Is there any problem in doing this?
> Can I just change it on my class and have it work when I deploy? Or is
> there a more manual migration step that has to happen? Here's a concrete
> example of the before and after I need to manage:
>
> Before:
>
>         public class Part {
>             public int Value { get; set; }
>             public int? Sides { get; set; }
>             public string Tag { get; set; }
>         }
>
> After:
>
>         public class Part {
>             public int Value { get; set; }
>             public string Sides { get; set; }
>             public string Tag { get; set; }
>         }

[EisenbergEffect]

That's what I thought....but I wanted to be sure. Awesome. Really wonderful.

[Jeremy Holt]

I do this all the time. If the database isn't too large, I simply write a loop that just loads and stores the document again. Boy is this faster than developing in SQL :)

var query= session.Query<Contracts>().ToList();

foreach(var contract in contracts)

{

session.Store(contract)

}

session.SaveChanges()

[Chris Marisic]

For future readers, remember that RavenDB is not a stupid orm and is safe by default.  session.Query<Contracts>().ToList(); will not pull your entire database into memory the way an ORM will, and that you need to handle batching properly. http://ravendb.net/docs/intro/safe-by-default