This is a discussion on ODBC connections without DSN within the Informix forums, part of the Database Server Software category; --> We are running IDS 10.00UC3 on RHEL 4 and are looking to upgrade to UC5. We have an application ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We are running IDS 10.00UC3 on RHEL 4 and are looking to upgrade to UC5. We have an application that connects to the database via ODBC. Unfortunately UC5 enforces the rule that the client app should have the same DB_LOCALE as the database. The client app has a hardcoded connection string which does not include the DB_LOCALE. Is there a way around this without changing either the code or the locale of the DB? |
| |||
| <tichman@excite.com> wrote in message news:1157403196.030071.225040@e3g2000cwe.googlegro ups.com... > We are running IDS 10.00UC3 on RHEL 4 and are looking to upgrade to > UC5. We have an application that connects to the database via ODBC. > Unfortunately UC5 enforces the rule that the client app should have the > same DB_LOCALE as the database. The client app has a hardcoded > connection string which does not include the DB_LOCALE. Is there a way > around this without changing either the code or the locale of the DB? Yes, there's an environment variable that you can set at oninit time that reverts to the pre-xC5 behaviour. Guy Bowerman wrote about it in his IBM blog: http://www-03.ibm.com/developerworks...e_with_locales |
| ||||
| Thank you very much. Setting the environment variable IFMX_UNDOC_B168163=1 reverts to the old behaviour of mismatched locales. Sheshnarayan Agrawal wrote: > There is developer work article written by Guy Bowerman which talks about > possible workaround. > > http://www-03.ibm.com/developerworks...e_with_locales > > The upcoming CSDK 2.90.TC6 release will have this issue addressed in ODBC. > Either you can use the workaround suggested in the above link or wait for > CSDK 2.90.TC6 to be released. By using ODBC from CSDK 2.90.TC6 you don't > have to change anything in your application related to DB_LOCALE setting > (If you are not explicitly setting DB_LOCALE in the connetion string which > anyway you mentioned you are not). > > Thanks > -Shesh > > > > > tichman@excite.com > Sent by: informix-list-bounces@iiug.org > 09/05/2006 02:23 AM > > To > informix-list@iiug.org > cc > > Subject > ODBC connections without DSN > > > > > > > We are running IDS 10.00UC3 on RHEL 4 and are looking to upgrade to > UC5. We have an application that connects to the database via ODBC. > Unfortunately UC5 enforces the rule that the client app should have the > same DB_LOCALE as the database. The client app has a hardcoded > connection string which does not include the DB_LOCALE. Is there a way > around this without changing either the code or the locale of the DB? > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > > > --=_alternative 002CC5C7652571E0_= > Content-Type: text/html > X-Google-AttachSize: 2222 > > > <br><font size=2 face="sans-serif">There is developer work article written > by Guy Bowerman which talks about possible workaround.</font> > <br> > <br><font size=2 face="sans-serif">http://www-03.ibm.com/developerworks/blogs/page/gbowerman?entry=trouble_with_locales</font> > <br> > <br><font size=2 face="sans-serif">The upcoming CSDK 2.90.TC6 release will > have this issue addressed in ODBC. Either you can use the workaround suggested > in the above link or wait for CSDK 2.90.TC6 to be released. By using ODBC > from CSDK 2.90.TC6 you don't have to change anything in your application > related to DB_LOCALE setting (If you are not explicitly setting DB_LOCALE > in the connetion string which anyway you mentioned you are not).</font> > <br> > <br><font size=2 face="sans-serif">Thanks<br> > -Shesh<br> > </font> > <br> > <br> > <br> > <table width=100%> > <tr valign=top> > <td width=40%><font size=1 face="sans-serif"><b>tichman@excite.com</b> > </font> > <br><font size=1 face="sans-serif">Sent by: informix-list-bounces@iiug.org</font> > <p><font size=1 face="sans-serif">09/05/2006 02:23 AM</font> > <td width=59%> > <table width=100%> > <tr valign=top> > <td> > <div align=right><font size=1 face="sans-serif">To</font></div> > <td><font size=1 face="sans-serif">informix-list@iiug.org</font> > <tr valign=top> > <td> > <div align=right><font size=1 face="sans-serif">cc</font></div> > <td> > <tr valign=top> > <td> > <div align=right><font size=1 face="sans-serif">Subject</font></div> > <td><font size=1 face="sans-serif">ODBC connections without DSN</font></table> > <br> > <table> > <tr valign=top> > <td> > <td></table> > <br></table> > <br> > <br> > <br><tt><font size=2>We are running IDS 10.00UC3 on RHEL 4 and are looking > to upgrade to<br> > UC5. We have an application that connects to the database via ODBC.<br> > Unfortunately UC5 enforces the rule that the client app should have the<br> > same DB_LOCALE as the database. The client app has a hardcoded<br> > connection string which does not include the DB_LOCALE. Is there a way<br> > around this without changing either the code or the locale of the DB?<br> > <br> > _______________________________________________<br > > Informix-list mailing list<br> > Informix-list@iiug.org<br> > http://www.iiug.org/mailman/listinfo/informix-list<br> > </font></tt> > <br> > --=_alternative 002CC5C7652571E0_=-- |