| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| JDBC vs ODBC discrepancy in mapping node(?) |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Wed Sep 12, 2007 9:15 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've heard of issues like this, where certain drivers or the product itself don't like it when the ODBC DSN is not named after the DB.
You are using the DataDirect driver for Oracle, not the Oracle driver for Oracle, right?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| PisgahMan |
| Posted: Wed Sep 12, 2007 10:14 am Post subject: |
|
|
Voyager
Joined: 27 Jul 2004
Posts: 93
|
| Yes, correct. Does the toolkit always and only use JDBC? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 12, 2007 11:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The database capabilities of the toolkit have absolutely nothing to do with Broker. They're entirely RAD stuff - that's been slightly leveraged for name resolution in the code validaters. At least, as far as I know.
The only real purpose for creating a database definition in the Toolkit is to cause it not to generate warnings on your code. But they're Toolkit only warnings, and easy enough to ignore.
I think you can configure a RAD/Eclipse database definition to use ODBC, but I'm not really sure.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
