Problem with dynamic use of schema name

Posts   
 
    
alex
User
Posts: 68
Joined: 30-Mar-2004
# Posted on: 11-Oct-2005 01:07:01   

I use a dynamic schema name assignment by setting the "schemaNameToUse" and "schemaNameUsageSettings" properties in the DataAccessAdapter. Everything worked fine before I upgraded to version 1.0.2004.2 (8/31/2005).

After upgrade, saving new entities generates the error "ORA-02289: sequence does not exist". I've checked the INSERT SQL statement that gets sent to the database and it contains the correct schema name. Unfortunately, I don't know how to look at the statement that selects from the sequence. I suspect that LLBLGen does not replace the schema name in the statements that select next value from sequences.

I tried to use runtime libraries from the latest upgrade (10/10/2005), but the problem still exists.

Please help.

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 11-Oct-2005 16:15:35   

Just for double checking, I'll just gonna repeat what was said in the following thread:

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=3726

1) be sure to re-generate your code with the new templates 2) be sure to use the new runtimes in production

And the latest is the important part as sometimes you may have problems with applications that still refer to old binaries

please check this thread: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=3619

alex
User
Posts: 68
Joined: 30-Mar-2004
# Posted on: 11-Oct-2005 17:27:16   

I use the following file versions: SD.LLBLGen.Pro.ORMSupportClasses.NET11.dll - 1.0.20042.50708 SD.LLBLGen.Pro.DQE.Oracle.NET11.dll - 1.0.20042.50605

Is that what I should have?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39898
Joined: 17-Aug-2003
# Posted on: 11-Oct-2005 20:48:26   

alex wrote:

I use the following file versions: SD.LLBLGen.Pro.ORMSupportClasses.NET11.dll - 1.0.20042.50708 SD.LLBLGen.Pro.DQE.Oracle.NET11.dll - 1.0.20042.50605

Is that what I should have?

The latest upgrade has newer versions, but nevertheless, you should turn on tracing for the DQE to see what queries are generated. In there the sequence query is shown as well. See troubleshooting and debugging in the manual.

Sequence schema names are also overwritten when you specify schema name overwriting. This was fixed some time ago, perhaps your code worked with the code before the bugfix and now you have the bugfix, the sequences aren't found anymore because the schema name is overwritten as well, and sequences aren't found anymore.

Could you please check that for me?

Frans Bouma | Lead developer LLBLGen Pro
alex
User
Posts: 68
Joined: 30-Mar-2004
# Posted on: 11-Oct-2005 23:06:14   

I've checked the link that Walaa gave me. It points to the forum discussion about the same problem as mine. This problem was fixed by you, Otis, on July 21st. I've downloaded and installed the 1.0.2004.2 version on July 18th which means that I don't have the fix.

I'm going to download and install the latest upgrade (Release date: 10-oct-05) . Hopefulley the problem will go away.

I'll let you know.

Thanks for your help

alex
User
Posts: 68
Joined: 30-Mar-2004
# Posted on: 12-Oct-2005 01:23:13   

It worked!

Thanks a lot.