> I'm still not convinced. Sure you can ensure the field is de-facto PK, > but as it's more walking on thin ice than robust design I think you, > as developer, should modify your model accordingly and keep it.
The biggest problem is views. You said that you don't include views into model because lack of information about keys. I've just made test database with one table and one view based on this table. After that i've tried to import model and make my view working in EF. For this i should: 1) Add EntitySet in EntityContainer in SSDL 2) Add EntitySet in EntityContainer in CSDL 3) Uncomment EntityType in SSDL 4) Add key fields in SSDL 5) Add similar EntityType in CSDL (with key fields). 6) Correct design of model in designer. Dou you think it's normally if programmer will make all this??? Do you think it's easy to make such changes on real database??? It's funny that almost all of this programmer should repeat after updating model from database!!! It's not seriously. It's not a wokk - it's a hell. This is real reason why we choose MSSQL instead of firebird. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
