|
|
jovball
User
Location:
USA
Joined on:
23-Jan-2005 19:53:47
Posted:
393 posts
|
This is for 5.2 (5.2.1) RTM.
We are attempting to use a sequence in DB2. This is our first time using that with DB2 and LLBLGen. (We have used it previously with SQL Server and LLBLGen).
The call works correctly in our development environment which has the base schema name used for LLBLGen code generation. However, in other environments where the schema name is different, the db2SchemaNameOverwrites is not working.
IOW, the call looks like this
| Code: |
SELECT NEXTVAL FOR DEVDB.MY_SEQ1 FROM SYSIBM.SYSDUMMY1
|
But it should look like this
| Code: |
SELECT NEXTVAL FOR PRODDB.MY_SEQ1 FROM SYSIBM.SYSDUMMY1
|
|
|
|
Walaa
Support Team
Location:
Joined on:
21-Aug-2005 16:03:48
Posted:
14529 posts
|
Please post the db2SchemaNameOverwrites config section.
Do you have it in the config file of the application (executable project)?
|
|
|
jovball
User
Location:
USA
Joined on:
23-Jan-2005 19:53:47
Posted:
393 posts
|
I don't think that's the issue. All other queries are correctly overwriting the schema name. It's only the sequence call that is failing.
Here's what the config sections look like. I've replaced the actual values with fake values.
| Code: |
<configSections>
<section name="db2SchemaNameOverwrites" type="System.Configuration.NameValueSectionHandler" />
</configSections>
<db2SchemaNameOverwrites>
<add key="DEVDB" value="PRODDB" />
</db2SchemaNameOverwrites>
|
|
|
|
Otis
LLBLGen Pro Team
Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37631 posts
|
|
|
Otis
LLBLGen Pro Team
Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37631 posts
|
|
Fixed in hotfix 5.2.4 / 5.1.7 (now available on the website)
|
|
|
jovball
User
Location:
USA
Joined on:
23-Jan-2005 19:53:47
Posted:
393 posts
|
Yes, that fixed the problem. 
Thanks for the quick response.
|
|
|