We are currently developing a new WinForms application (C # .NET 3.5).
Currently, the project is 40% completed, however, we spend a significant amount of time on the implementation of the DAL (CRUD) implementation. Now we want to move NHibernate as an ORM solution to take advantage of its many advantages and to facilitate some of the work of DAL coding.
We would rather focus on solving business problems.
We are currently planning to upgrade to NHibernate and FluentHibernate, but you have a few questions.
Is NHibernate changing to a steep learning curve? In terms of performance, do you think NHibernate would be a smarter option than continuing to write our own?
We currently use soft deletion and read data through views in the database that have the field "Deleted = null" (Deleted is TIMESTAMP). As far as I understand, when we map each class, we can also indicate the sentence "Where", which means that we no longer need any "filtering" views in our database? It is right?
In connection with the question above. We also have a “Clear” function that can delete records from the database. Can we use soft deletion and still have a cleanup function?
Can we save blobs in a database through NHibernate?
? NHibernate, , , . -, NHibernate , ?
NHibernate Lookup? , . NHibernate.
, , NHibernate.