This is the client requirements.. as i understand it stems from the fact that the application will be installed at multiple locations, and some have sqlserver while others have oracle.
On Mon, Oct 13, 2008 at 4:04 PM, Ken Egozi <[EMAIL PROTECTED]> wrote: > I really don't get the need to swap RDBMSs. > I mean, really. how many times in a lifecycle of a majot application does > one switches his high-cost Oracle servers into the > not-as-high-but-still-high-cost MS-Sql? or from Postgres to MySql > whaterver? usually it'd be a kind of a strategical desicion that will be > accompanies by business changes -> thus a change to the app anyway. > > Especially doesn't make sense in switching Oracle/SqlServer. Both are > pricey (one of them rediciulusly pricey), and you'd spent the dimes if you > want to squeeze some special things that only this said server can give you. > So you end up with special PL-SQL/T-SQL code that needs to be migrated > anyway. > > My stance is that if you didn't get to the point of needed the propriety > stuff in the DBMS, then you don't have any reason to switch DBMS anyway, cuz > you won't use the propriety stuff in the target system anyway. and if you > will, then it's a change in the application anyway, so why bother with > "switchability" to begin with? > > > End Rant > > > > > unless you write a simple application that will get installed on many > places, and even then for low-needed scenarios I'd go with an embedded > Firebird / SQLite or SQL Express installation, while for large > > On Mon, Oct 13, 2008 at 3:50 PM, N. D. <[EMAIL PROTECTED]> wrote: > >> We have a similar scenario, 2 teams considering both EF and NH, but the >> determining factor is Oracle support and ability to switch SqlServer/Oracle >> seamlessly. >> >> >> >> On Mon, Oct 13, 2008 at 3:41 PM, Scott Belchak <[EMAIL PROTECTED]> wrote: >> >>> Tuna, >>> I was recently brought on board to General Mills HQ to help their >>> "Microsoft Center For Excellence" team determine which ORM tool to use. My >>> sole purpose at this contract is to re-develop one of their existing >>> websites in Entity Framework and NHibernate side by side so that they can >>> compare the two when they are done. My initial plan was to do a repository >>> pattern with IoC containers to do the switch between which Repo the website >>> should consume, but had such a hard time separating concerns with the Entity >>> Framework that we decided to scrap the EF portion of the project for the >>> website and just use NHibernate. They will be proving out the entity >>> framework with a WCF application instead. >>> >>> So, if all goes well, and I do a good job showcasing the wonders of >>> nhibernate, you will have a really smart team at General Mills pushing >>> NHibernate to all of the other teams here. >>> >>> I'll let you know how everything goes after the contract is over. >>> >>> >>> On Sun, Oct 12, 2008 at 8:07 AM, Tuna Toksöz <[EMAIL PROTECTED]> wrote: >>> >>>> Hello, >>>> >>>> As you may notice >>>> here<http://groups.google.com/group/nhusers/browse_thread/thread/7e05fa56121a500>, >>>> we want NH to be prefered over other alternatives and one way to show this >>>> is to have some names of firms used it successfuly. To say the truth, there >>>> are _many_. But none of them show up when you do a search. >>>> >>>> In short, we need success stories to collect, if you have one, please >>>> don't hesitate to send it here. >>>> >>>> Your contributions are all welcome. >>>> >>>> -- >>>> Tuna Toksöz >>>> >>>> Typos included to enhance the readers attention! >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > -- > Ken Egozi. > http://www.kenegozi.com/blog > http://www.musicglue.com > http://www.castleproject.org > http://www.gotfriends.co.il > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
