Problems changing Oracle schema's name

Posts   
 
    
CaptainJeP
User
Posts: 1
Joined: 19-Aug-2004
# Posted on: 05-Nov-2004 17:06:48   

Hi,

We have generated the two classes scenario with schema X (integration environment). It works well on that schema, but it doesn't work when we change the connection string to use the same DLL on schema Y (production environment). We found that the oracle schema name was hardcoded multiple times in the FactoryClasses\EntityFieldFactory.cs . We found and replaced these strings, but it was not enough.

How can we change the name of the schema without regenerating?

Thanks

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39749
Joined: 17-Aug-2003
# Posted on: 05-Nov-2004 17:26:14   

The schema name is indeed hardcoded in the persistence info. To change it, either: - go to the designer, catalog explorer -> select the schema, hit F2 and rename it, -> generate or: - download the Oracle Team Development templates from the customer area on the website (it's at the bottom of the list) in the 3rd party section, read the enclosed readme and re-generate your code with that template set. The templates are for the templates released after sep 24. or: - replace the name in the EntityFieldFactory.cs file. That's the only file where persistence information is stored.

Also be sure you change the right connection string value, i.e. the one in your application's .config file, not the app.config in the generated code.

Frans Bouma | Lead developer LLBLGen Pro
asgeirgs
User
Posts: 8
Joined: 09-Sep-2008
# Posted on: 06-Jan-2009 15:57:29   

Otis wrote:

The schema name is indeed hardcoded in the persistence info. To change it, either: - go to the designer, catalog explorer -> select the schema, hit F2 and rename it, -> generate or: - download the Oracle Team Development templates from the customer area on the website (it's at the bottom of the list) in the 3rd party section, read the enclosed readme and re-generate your code with that template set. The templates are for the templates released after sep 24. or: - replace the name in the EntityFieldFactory.cs file. That's the only file where persistence information is stored.

Also be sure you change the right connection string value, i.e. the one in your application's .config file, not the app.config in the generated code.

Is this still an issue in the current version. I need to be able to dynamically switch between schemas without needing to re-generate or re-compile. I need to be able to do this from the app.config file of the EXE.

How do I do that ?

Thanks, Ásgeir Stefánsson

MTrinder
User
Posts: 1461
Joined: 08-Oct-2008
# Posted on: 06-Jan-2009 23:20:56   

Like this - Schema Name Overwriting

Generally it is better to start a new thread rather than "hijack" an old one as we won't always notice it.

In addition, the Architecture forum is not as closely monitored for support issues as the others - it is more intended for discussions.

Matt