Re: Java vs .NET was: RPGIII compiler vs Visual Basic

On 6/21/05, Joel Cochran <jrc@xxxxxxxxxx> wrote:
> > date: Tue, 21 Jun 2005 12:54:33 -0400
> > from: Steve Richter <stephenrichter@xxxxxxxxx>
> > subject: Re: Java vs .NET was: RPGIII compiler vs Visual Basic
> 
> > > DBAccessManager db = new DBAccessManager(
> > >        SWallTech.DB.DatabaseTypes.iSeriesDB2 ,
> > >        datasource ,
> > >        database ,
> > >        userID ,
> > >        password ,
> > >        securityType );
> >
> > looks great Joel, but it is too much code!  The strength of .NET is
> > its simplicity and consistency.  A shop pays an extra $20 per month.
> > In return its team of $70 per hour contract programmers get their work
> > done sooner which saves the enterprise a lot of money.
> 
> Too much code?  Why, because it takes parameters?  This is just
> instantiating an object, how much simpler do you want it?  Your initial
> complaint was needing to write different code for MySQL vs. SQL
> Server... this way, you use the same class for ANY database you want to
> access.
> 
> The complexity is hidden: developing the connection string, creating the
> xxxConnection object, creating and using xxxCommand objects, etc., are
> all encompassed in the database classes, which you only have to develop
> once.  To me, this is exactly the consistency and simplicity you are
> looking for.

I am curious to know how it would be done.  In the end however, the
simplicity of using SQLServer only wins out.

> 
> > ( I was going to suggest you derive your data access classes from
> > SqlCommand and SqlConnection.  But I see that MS has sealed those and
> > many other .NET classes.  Which means they cant be derived.  Which
> > makes it harder to use MySQL in .NET code! )
> >
> > -Steve
> 
> The way ADO.NET works, you access the database you want through a
> "Managed Provider".  That managed provider is a series of classes that
> the database vendor (or some third party) wrote so that you can access
> their database in .NET using the ADO standard.  As a result, they all
> have their own class names:
> 
> iDB2Connection
> MySqlConnection

a lot snipped

> 
> If that is too much code for your contractors, then I suggest you get new 
> contractors.
> 

or use SQLServer as the sole database for .NET applications.

-Steve


> Joel
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>