Hows it going,
Firstly I hope that this slightly general question is ok. It is related to using NHibernate.
Recently I've been looking at designing a data model for a company. Initially I was following a traditional data modelling lifecycle. Identified the entities in the domain, build a logical model and abstracted down to a physical model where I added things like FK's, Triggers, etc, etc.
This has always worked well for me designing and building Oracle applications and J2EE apps in turn using Hibernate between the App and Database.
However one of the applications to use the DB (MSSQL 2005) is going to be A RIA built in Visual Studio. Seemingly C# has some cool types like radio button list, drop down list and check box list that all inherit from some super type.
This means that you could have a table containing artifacts that are displayed on a form. As you add/remove artifacts from the table they are dynamically added to/removed from the form.
So...
My question is, does this fundamentally change how data models are developed since
A) You create the data model based on how your forms are going to turn out
B) You stick to the traditional way of modelling the domain and use your ORM tools to write/to from your application to the relational database tables. Taking into account CRUD operation performance, etc, etc
C) What about new tools like WebGrid for .NET, what implications does this have for data modeling?
I hope this isn't too convoluted!!
|