Re: Java and JDBC vs 4gl

I don't know much JDBC but I think JDBC solely can't beat a 4gl, I mean: I don't expect a JDBC port of a 4gl batch could perform better without some aditional tricks... May be you can try to issue and "SET ISOLATION TO DIRTY READ" inside your JDBC... that way you won't have -243 errors... and it's faster of course but it's dangerous if the logic of you algorithms doesn't allow... Other way I think is to catch that -243 as a java exception... and ignore that message and resume your processing... althoug maybe a redesign of your algoritms may be needed... Chucho! -----Original Message----- From: "Ph. Chantry" <sorry.nomail@mail.fr> To: informix-list@iiug.org Date: Fri, 21 Nov 2003 11:03:42 +0100 Subject: Java and JDBC vs 4gl Hi all, We plan to migrate our 4gl (7.31) batch programs from 4gl to Java (2.21.JC4). Our tests show us that the connexions on IDS server through JDBC are very slow compared to the connexions established by 4gl batches. Is it a know behaviour/bug ? For example, we have to perform the following requests in several parallel loops: - insert one row in tableA - update one row in tableB Both tables are in "lock mode row". Each loop accesses the same two tables, in a random way, so thah rows in tableB may be accessed concurrently. The connexions are established with "set lock mode to wait 1". With JDBC connexions, we observe very often error "-243 Could not position within a table, ISAM error -154" on the update statement. We never observe it with 4gl connexion. The error does no more appear with JDBC connexions with "set lock mode to wait 10." Any idea to accelerate the JDBC connexions ? Have we missed some settings ? Thank you, Philippe Jean Sagi jeansagi@myrealbox.com jeansagi@netscape.net sending to informix-list