The EntitySpaces Community

Share and learn about the EntitySpaces Architecture.
Welcome to The EntitySpaces Community Sign in | Join | Help
in
Home Forums Photos

Choice of Oracle provider

Last post 05-11-2007, 5:33 AM by trihanhcie. 4 replies.
Sort Posts: Previous Next
  •  02-03-2007, 3:14 PM 97

    Choice of Oracle provider

    Is there anyway I can use System.Data.OracleClient in place of Oracle Provider For OLEDB? What is/was the reasoning for using an external provider and not the inbuilt .NET framework Oracle provider?
  •  02-03-2007, 7:30 PM 102 in reply to 97

    Re: Choice of Oracle provider

    EntitySpaces itself does use System.Data.OracleClient however it's MyGeneration that uses OLEDB. The reason is that OLEDB supports an API known as schema rowsets, and this API returns all of the meta data for a given database, in fact, most databases support Schema Rowsets. If you need the Oracle OLEDB driver for MyGeneration you can find them for all versions on the Oracle site, however, again, EntitySpaces doesn't use OLEDB.  I hope this helps ...

    EntitySpaces | Twitter | BLOG | Please honor our Software License
  •  05-11-2007, 2:34 AM 2335 in reply to 102

    Re: Choice of Oracle provider

    How can you use Mygeneration with Entityspace and Oracle then?

    I tried to add the following connection string in the web.config:

    <add name="TEST" providerMetadataKey="esDefault" sqlAccessType="DynamicSQL" provider="EntitySpaces.OracleClientProvider" providerClass="DataProvider" connectionString="..." >

     The generated code using MyGeneration is not working because, as said earlier, entitspace use System.Data.OracleClient while Mygeneration uses OLEDB

    What i need is a connectionstring exemple i think

  •  05-11-2007, 4:41 AM 2337 in reply to 2335

    Re: Choice of Oracle provider

    Think of MyGeneration and EntitySpaces a seperate products (and they are). You asked "How can you use Mygeneration with Entityspace and Oracle then?" but in reality there is no issue here. MyGeneration merely generates the EntitySpaces Source Code, EntitySpaces could use ODBC if it wanted to. MyGeneration uses OLEDB providers (mostly) because OLEDB drivers provide a wealth of metadata. Here is an example ORACLE connection string for MyGeneration (you use use the OLEDB button in MyGeneration to connect)

    • MyGeneration Connection to Oracle 

    Provider=OraOLEDB.Oracle;Password=mypassword;Persist Security Info=True;User ID=Griffinski;Data Source=orcl 

    • EntitySpaces Connection to Oracle (just use a normal OracleClient connection string, it's documented in the MSDN Help as well)
    Password=mypassword;Persist Security Info=True;User ID=Griffinski;Data Source=orcl; 


    EntitySpaces | Twitter | BLOG | Please honor our Software License
  •  05-11-2007, 5:33 AM 2341 in reply to 2337

    Re: Choice of Oracle provider

    I tried the connection String and i've got the following error : ORA-01741 and a message saying  illegal zero-length identifier.

     

     

     

    I found it, I had to uncheck "metadata class should ignore schema and catalog" in mygeneration to make it work.

     Thanks

View as RSS news feed in XML