I see a lot of work at the moment on Entity Modelling in Code and interest in functional Programming. After some years working in Object Oriented Systems I have time and time again come up against the "Impedance Mismatch".
Since Transact SQL implements some FOP with datasets being described as Sets in a declarative way, does the "impedance mismatch" go away. If this is the case, which I am trying to ascertain, is there a need for the Domain Model being developed in code or is it ok to use the old and tried techniques of SQL and relational theory.
I know there is a big push in writing Entity Layers and ORMS at the moment to try and mitigate this impedance mismatch and get systems to work as Objects.
Does this work around reflect that there may be a bigger issue at hand and the "Impedance mismatch" is a lot more concerning for Object Oriented Design/Programming in that the whole paradigm might not be the best solution when dealing with RDBMS interactions.
I am thinking of the implications of moving from c# over to f#, full time and for all code bases. I think that I might have a problem with shifting my mind set.