1) I am trying to import an existing postgresql database that has many stored procedures that are overloaded; i.e. using the same procedure name only differing by the input paramter. The import fails because the datbase import wizzard does not recognize the differnces in functions based on input parameters, only by the name. Is this a limitation, or something I am doing wrong?
2) The other issue I have is that I don't want the import to change the names of any tables, parameters or functions. When it does, it breaks about 100,000 lines of code. I have tried every way I can imagine. Using leave unchanged still changes table names by capitilizing the first letter. Setting to all lowercase does the same thing. Is this by design?
3) Thank you for making this tool free, if I can get it to work, it will be amazing. I am trying to take an existing database design that I have in both MYSQL, ORACLE and POSTGRESQL and conert to MSQL and Azure. Out of all of these, what would be more likley to give me the least issues?
Thanks Telerik,
Jason
5 Answers, 1 is accepted
Firstly I want to apologize for the inconvenience caused.
1. We have successfully reproduced the wrong behavior and found the cause for the issue. The fix for the problem will be included in the next official release of the product.
2. I am afraid that this is a known issue. We will do our best to fix the issue and improve the behavior for the next release.
3. It will be easier if you try to convert to MySQL model to MSSQL.
Hope that helps.
Damyan Bogoev
the Telerik team
Rank 1
You need not appologize, but rather I should thank your company for having such a great free ORM! I am excited to use it indeed. As you can imagine, my next question is, "When is the next release going to be out?"
Are there any work-arounds?
Thank you!
Jason
The next major release of the product is scheduled for October. But we will release service pack before the release.
Actually you could re-create your domain model in order to import the overloaded procedures. In this scenario all the selected stored procedures will be created in the model.
If any other questions arise, do not hesitate to contact us back.
Damyan Bogoev
the Telerik team
Rank 1
Thank you again; when you state that I could re-create the domain model as a work-around can you be more specific? Do you mean to create each property and table in the designer by hand again with the assocations? If that is what you mean, then I assume that the bug is only related to building a model based on an existing database, is that correct?
The bug is based on merging the selected changes from the Update from Database wizard to the existing domain model, when there are overloaded stored procedures.
There is an issue in the unique stored procedure key generation functionality. We will fix this issue in the next release of the product.
Damyan Bogoev
the Telerik team