Re: Powerbuilder-Informix

> > I followed your discussion about Powerbuilder and Informix, > getting a little bit confused. > We are using PB and Informix too. > > We are using PB 4.05 (just migrating to PB5). > The DB-Connection is done by > Intersolv ODBC 2.0x and Informix NET-PC 5.01. I am not sure why you have the problem with Informic Native Drive 5.01. We have been using 5.01 with Powerbuilder 3.x, 4.x, and 5.x since 1994. 5.01 did have memory leakage problem. I am not sure whether it is fixed now. But the memory leakage does not affect us most of the time. There is another patch with regard to a TCP-IP issue. As far as I know, that is not informix's bug. > > You ask me why! > > Later Versions of Informix NET-PC don't support multi-transaction > connect in one application. So you can use only one ( 1 !!!) > transaction-object per application. (It's a feature, not a bug :->>>). First of all, our development team is currently using two connections with two transactions running at the same time. It works. But it is a bad idea (it is not my idea). After the two transactions were implemented, the team found they have problems to make the two transactions in-sync. What if one transaction is committed, the system crashes before the other transaction commits. This is the exact reason why multi-transactions is not a good idea. If you check out all the text books about transaction processing. The majority of the text book focuses on how to merge multiple transactions into a single serialized process. How to resolve the synchronization of multiple transactions is a very technical issue, and it is certainly not Informix's issue. In fact, because it is so technical that it creates a whole market and the leading product for this market is Tuxedo. Even without Tuxedo, Informix can still resolve the problem for you, if you handle operations through stored procedures. Informix will handle all the synchronization for you through two-phases commit. But if you want to handle through your PowerBuilder code. Talk to powerbuilder (Again, I-NET 5.01 supports multiple connections and hence multiple transactions). Powerbuilder does not support two-phase commit. Hence, the multiple transactions support from Powerbuilder is just a hype from PowerBuilder. > > Later Versions of Intersolv ODBC don't work very good. We had a > version that did't show the indexes of the tables. > > Last but not least... > We don't use the pb informix native driver, because it doesn't work. > There are some handshaking-problems wih it. The client-application > doesn't wait long enough for the result of an db-request. > And the Null-Column-Attribute isn't mapped too. > Again, our pb informix native driver works starting from pb 3.x. Please tell us more about why your pb informix does not work. Chao