Elegant coding: 09/01/2004

The difference among different DotNet data provider for oracle
There are three major data provider from Oracle, Misrosoft and Borland
1) if we run a query to return same amount of rows, the ODP.net would take the shortest time, while BDP.net would take the longest time.

2) All of three providers are based on ADO.NET, this means they have same basic classes and methods,
If we are going to replace MSDP.NET with ODP.NET, what we need to do is changing the library reference and the units in uses section,
But they also have some slightly difference, for instance, the oracle data type for ref cursor in MSDP is OracleType.cursor, and
the oracle data type for ref cursor in ODP is OracleDBType.RefCursor

3) All of three providers support Ref Cursors returned by Oracle stored proc

4) Both of MS data provider and Oracle data provider support database connection pooling, but Borland Data Provider doesn't support it

5) MS data provider offers an OracleLob object that handles all Oracle LOB database objects in the same fashion, while the Oracle data provide offers
specific objects for both Oracle BLOB and CLOB database objects. This means ODP.NET provides better support for these Oracle datatypes.
For instance, the OracleClob object overrides the read method to populate a char array. This feature is especially useful when dealing
with Unicode and other multibyte characters.

6) The MS data provider come with DotNet framework, and the DotNet framework is part of in windows XP professional and windows 2003 server .
whereas Oracle data provider or Borland Data Provider need to be installed separately

Tuesday, September 14, 2004

WS Spec

Inversion of Control Containers and the Dependency Injection pattern

Sunday, September 12, 2004

Joel on Software - How Microsoft Lost the API War

I don't think the Web page will be instead of Win GUI, although some web pages are fancy enough, but please just take a look the JavaScript code, it is extremely long, and quite badly organized.

whereas I think that Avalon and Indigo will be instead of Web page if M$ could do their work well, what my desired GUI is that it has no round trip, no overall refresh, and no deployment.

the thing I worry about is M$ current GUI project strategy, WinForm semms as if to be stillborn. infopath, a very cool stuff, but nobody use. Avalon need to wait at least two years. why M$ can't focus on one thing.