SQL CE Codefirst not generating columns for enum types

Question

This is somewhat new territory for me.

I'm using MVC3 with SQL CompactEdition version 4.0 and EntityFramework version 4.1 (with CodeFirst), and MVC Scaffolding by Steven Sanderson (although I don't think that last point is relevant).

I've got several different model classes that have properties that are enums. I find that when CodeFirst generates the schema for those tables, there is no column corresponding to those properties.

What's the correct way to handle this situation?

Diego Mijelshon · Accepted Answer · 2011-06-06 02:33:09Z

3

EF does not support enums, plain and simple.

The easiest workaround is having a mapped property that converts the enum to/from a string or int (depending on how you want to store the values)

The alternative, of course, is choosing a more mature framework (NHibernate is the one I like, but there are others)

answered Jun 6, 2011 at 2:33

Diego Mijelshon

52.7k16 gold badges119 silver badges159 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Dave Hanna Over a year ago

So define the model object with two properties, one of which is a string or int with automatic getter/setter, and the other is the enum with a getter/setter doing the mapping? Or can I simply define one property that is the enum with a getter/setter mapping to an explicitly defined string or int backing store? (i.e., does EF work only with properties, or can it work with the underlying fields?)

Diego Mijelshon Over a year ago

@DaveHanna: AFAIK, EF works with properties. As long as you expose something it recognizes, you can define the backing storage any way you see fit.

Collectives™ on Stack Overflow

SQL CE Codefirst not generating columns for enum types

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related