This question is locked. New answers and comments are not allowed.
I was trying Telerik ORM (2010 Q3) with Oracle Database (Oracle ODP.NET) in order to use an Oracle Database. I was doing it with success.
Today, I've installed Telerik's ORM last version (2011.1.316.3). The screens where I configure the connection are diferent, and now when I chose the Oracle Backend there I can't see my VS2010 connections using ODP. In Telerik ORM (2010 Q3) I could use those connections.
When I choose to make a new connection the ORM is using an older Oracle Driver and I can't access the Database like I used to.
Can you please help me?
Note: I've attached the printscreen's relative to the former and newer ORM version. older works, newer doesn't.
Regards
Carlos Sampaio
Edited: I've copied the connection string from the older aproach, and I managed to access the schemas, and after, the tables, but it takes about 5 minutes for list the tables (arround 20) when in the previous was much faster... Either the way I'm happy to achieve to get the tables... I'll try to use them now.
Edited 2: Managed to get the model. The second time I tried was much faster.
Still I have you feature I can't get to use as I wanted (newer or older ORM version):
- I have an Oracle Database
- The names of the tables are all capital letters as the fields
- I can't get an autogenerated names that are camelCase for Properties and PascalCase for Classes when removing underscores and identifying underscores as delimiters. Why? Because the algorith telerik uses doesn't turn all names into lower letters before appliyng the transformations. Example
Table: CUSTOMERS_INFO
Fields: ID, CUSTOMER_NAME, CUSTOMER_AGE
Results:
Table: cUSTOMERSINFO
Fields: iD, cUSTOMERNAME, cUSTOMERAGE
Wanted:
Table: CustomersInfo
Fields: iD, customerName, customerAge
Today, I've installed Telerik's ORM last version (2011.1.316.3). The screens where I configure the connection are diferent, and now when I chose the Oracle Backend there I can't see my VS2010 connections using ODP. In Telerik ORM (2010 Q3) I could use those connections.
When I choose to make a new connection the ORM is using an older Oracle Driver and I can't access the Database like I used to.
Can you please help me?
Note: I've attached the printscreen's relative to the former and newer ORM version. older works, newer doesn't.
Regards
Carlos Sampaio
Edited: I've copied the connection string from the older aproach, and I managed to access the schemas, and after, the tables, but it takes about 5 minutes for list the tables (arround 20) when in the previous was much faster... Either the way I'm happy to achieve to get the tables... I'll try to use them now.
Edited 2: Managed to get the model. The second time I tried was much faster.
Still I have you feature I can't get to use as I wanted (newer or older ORM version):
- I have an Oracle Database
- The names of the tables are all capital letters as the fields
- I can't get an autogenerated names that are camelCase for Properties and PascalCase for Classes when removing underscores and identifying underscores as delimiters. Why? Because the algorith telerik uses doesn't turn all names into lower letters before appliyng the transformations. Example
Table: CUSTOMERS_INFO
Fields: ID, CUSTOMER_NAME, CUSTOMER_AGE
Results:
Table: cUSTOMERSINFO
Fields: iD, cUSTOMERNAME, cUSTOMERAGE
Wanted:
Table: CustomersInfo
Fields: iD, customerName, customerAge
1 Answer, 1 is accepted
0
Hello Carlos,
In the new version we have changed the face of the wizard, however the code used to read the database schema underneath is the same. There should be no difference in the speed of reading.
Regarding the Connection Properties dialog that pops up after clicking the Add New Connection button, you should be able to switch to ODP.NET (the old screen) if you click the Change button and select ODP from the list of available data sources.
We are aware of the naming problem you described and unfortunately cannot provide you with a solution for the field names which you want to start with a lower case letter. The problem is that at the moment each capital letter is considered as new word. We will add this functionality for one of the following versions of the product.
There is, however, a solution for the class naming, and it is to use the Capitalize case mode and enable the Remove underscores and Interpret underscore as word delimiter options. In this case the outcome of CUSTOMERS_INFO would be CustomersInfo. I hope that helps.
Best wishes,
Alexander
the Telerik team
In the new version we have changed the face of the wizard, however the code used to read the database schema underneath is the same. There should be no difference in the speed of reading.
Regarding the Connection Properties dialog that pops up after clicking the Add New Connection button, you should be able to switch to ODP.NET (the old screen) if you click the Change button and select ODP from the list of available data sources.
We are aware of the naming problem you described and unfortunately cannot provide you with a solution for the field names which you want to start with a lower case letter. The problem is that at the moment each capital letter is considered as new word. We will add this functionality for one of the following versions of the product.
There is, however, a solution for the class naming, and it is to use the Capitalize case mode and enable the Remove underscores and Interpret underscore as word delimiter options. In this case the outcome of CUSTOMERS_INFO would be CustomersInfo. I hope that helps.
Best wishes,
Alexander
the Telerik team