We have a legacy mainframe system that we interact with using a proprietary SQL-like grammar. We have a ton of legacy code written against this. We also have a great deal of Oracle based systems as well as SQL Server. Consolidating technology, simplifying how we interact with the mainframe, and having a uniform programming model across our various applications are our goals. There are a number of NH features around change tracking, multi-level cache, and persistence ignorance programming model that are very attractive for our mainframe programming model.
Not surprising, NH seems to be pluggable at many levels including dialect that might allow me to pull this off. Wondering if this is a path that will lead to dragons or fruit. Any examples of NH being used to front non-relational data stores? Any thoughts appreciated. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/uGikX8j1RwsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
