Actually to clarify, I am more interested in the actual driver speed, like the time it takes to connect, or send a query over etc. (not how much faster/slower mysql versus sqlserver is).
I was reading how EF was not very good with mysql, and was interested to know if nhibernate with mysql is production ready for high traffic environments. On Mon, Aug 15, 2011 at 12:05 PM, Jason Meckley <[email protected]>wrote: > probably not as that wouldn't do much good. to start NH is more than just a > way to write sql statements. there's caching, proxies, change tracking, > optimistic locking, etc. this applies to any relational database it's > talking to. so adding NH only distorts the results. a more appropriate > comparison would be between mssql and mysql. both are mature platforms and > each has different strengths and weaknesses. I would bet that most, if not > all of, the comparisons that really matter have nothing to with performance. > for example: cost, availability, scalability, administration. > > part of the reason for using an ORM is to remove the requirement of which > database to target. you are free to choose whichever one you want. > > -- > 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/-/OhiB790hs8oJ. > 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. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. 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.
