Oracle Provider for. NET expands ado.net 2 (ZT)

Ado|oracle vsm:oracle Objects for OLE (OO4O) is designed as an alternative to ADO, and it can do everything that JDBC does. The role of OLE DB and Ado.net is part of oo4o all features. OLE DB does not support the object data types introduced in Oracle 8. What about oo4o?
Demarest:oo4o supports object data types. And we think Ado.net also supports object data types. OLE DB is not supported because it was written on the old specification. ADO never uses a different interface. It is closed and is not extensible, as Microsoft has designed it to. That's why we are developing odp.net. Ado. NET cannot access all of the higher-level features in Oracle.

VSM: Not many developers use oo4o in a variety of ways, but they use it for XML functionality. Your, your. NET support also has all the features of oo4o?
Demarest: Many of our users chose oo4o over Ole DB because of its quality, scalability, and performance, as well as other features I talked about, such as advanced queues, handling Oracle object types, and new XML database performance. Oo4o is optimized for Oracle environments, and Microsoft offers functionality that is inherently more generic. Ado. NET specification gives us the opportunity to provide our own functionality to Windows developers. This is what we have. NET support. Our direction is to provide a comprehensive feature access. So the answer to your question is yes. We will support. NET according to the needs of our users.

VSM: In. NET, can you get the same level of XML support in Java?
Demarest: We are ready to provide our XML DB. That's our local XML database performance, published for Oracle 9i version 2. Now it's a beta release: it's going to be released in a year. The most important technical idea is that you can always use Oracle to make standard calls. VS developers always have a way to get our XML database, although it requires C or C + +.

VSM: Can you do those in C #?
Demarest: I'm not sure about C #. It may have access to the C + + class library.

VSM: Does Oracle think. NET users are second-class citizens compared to Java users? Many vs developers seem to think that all Oracle things are written in Java and do not take into account Windows APIs.
Demarest: I don't agree with that, I think Microsoft makes Java users a second-class citizen. Those. NET provides services that have similar capabilities--we support them. The Java EE specification is more mature/complete, so it needs more support. NET has been the goal of our progress. We need to blend. NET technology to make our products more convincing. Obviously Microsoft is privileged and can use operating system development completely and directly, and we can't. But we can usually stay in sync with Microsoft, so I think we're doing as well as any other company in terms of resources, white papers, seminars, and product offerings.
Oracle is primarily a technology infrastructure company for enterprise processing. The user wants a secure structure, so we don't want to release anything until everything is ready for the production environment. Take a look at all the content that the Windows Development Center provides on the Oracle Technology Web site. We are very active.

VSM: It is difficult to integrate object data type support in. NET; data sets make this work difficult to complete. Do you support this?
Demarest: Object data type support is currently in the evaluation period. There seems to be no quick way to accomplish this task in. Net. If it reaches critical mass, we will support it.

What are the benefits of Vsm:blob support? What about REF cursors support? Can you update a small portion of the blob and then respond to the updates you have made?
Demarest: We have provided comprehensive support for this in odp.net.

VSM: Do you also support Unicode?
Demarest: Yes. It is included in all of our versions, as well as in the Odp.net beta release.

What about the performance of VSM:ODP.NET?
Demarest: Pretty good! This is always one of our important standards. We hope and expect our provider to excel in ADO and OLE DB.

VSM: Do you support COM + transactions in odp.net?
Demarest: Yes-it's already in the beta version. Oracle is more cautious in the beta version than Microsoft. The quality of most of our beta products is the same as the quality of the products that Microsoft has released. The method we use is to customize a Alpha/beta program for an uncertain thing. Microsoft's beta products are more for marketing than quality issues.

Vsm:visual Studio is hard-coded, so the only data provider that can be used for it is SQL client and OLE DB for SQL Server and access, right? In addition, an independent software developer (ISV) called Data Direct has written its own equivalent data provider, which you can install in Visual Studio. But it does not have as many functions as Oracle or Microsoft. And, of course, data Direct has a local data provider for Oracle. So is Oracle planning to write a unique Oracle attachment to Visual Studio?
Demarest: We are watching, but there is no report yet.

VSM: If you use Oracle's data provider, install it in Visual Studio, display an icon on the toolbar, and then drag a data adapter onto the designer surface, you won't succeed. It's not going to work. You are locked out of the IDE, so you can only write code in one line, is that right?
Demarest: That's another reason we want to integrate into Microsoft vs to generate Odp.net code. We want to solve this problem through Microsoft. may well be successful. Microsoft people like to have a closed environment and have their entire stack. So here I am not good to say.