Re: OLE DB Property Sets and Property Groups



Vivekanand (vivekanand_bachche@xxxxxxxxxxxxxxxx) writes:
The consumer allocates an array of DBPROPSET structures and passes this
array to the provider. Now supoose that the consumer calls
ICommandProperties::SetProperties to set some properties. The array of
stuctures it passes to the Provider contains two sets --
DBPROPSET_ROWSET and DBPROPSET_DATASOURCE. Is it valid to pass property
sets from different property groups while setting properties in one
group? Who is resposnsible for checking this validity?

Let me first say that I have never written a provider, only one consumer -
and that was quite thrilling itself.

What I would expect is that the OLE DB checks that the property set is
valid - which DBPROPSET_DATASOURCE can't for ICommandProperties. But if
there is a certain rowset property you don't like, you would have mark
that one invalid. Then again, it may be better to be safe and sorry to
check all properties.

Of course, testing what actually happens can't be that bad idea.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.



Relevant Pages

  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ERROR: Provider Management - Could not establish a connection to t
    ... If you have not yet created the SQL Server database, ... Can any data provider be used to ... Exception Details: System.Data.SqlClient.SqlException: A connection ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: for oxford- vz fading away?
    ... marketplace barriers to adopting a new/different Service Provider. ... For the average consumer, how is he expected to realistically remain ... Does he risk going through the entire hassle of switching, ... indifference / fear of hassles when switching / etc ... ...
    (comp.sys.mac.advocacy)
  • Re: .NET data provider or OLEDB provider?
    ... >I don't see where you see a built-in query engine. ... >service provider, ... >OLE DB providers don't have to support SQL however, ... > SQL Server linked server, SQL Server can handle the queries. ...
    (microsoft.public.data.oledb)
  • Re: Need Help: Operating system error 3706
    ... Installing an additional component resolved the problem and the software is now able to connect to the database ... The developer is currently doing a complete rewrite/update of the program, including database functions. ... While this would require a modest re-write, it's not that tough to convert to a managed-code provider instead of the COM-based OLE DB provider. ... If the application is not based on .NET, then make sure the application is upgraded to use the SNAC (SQL Server Native Client) provider which is less trouble-prone than the older MDAC-based providers. ...
    (microsoft.public.sqlserver.connect)

Loading