Multiple Sessions and the DBMS
Each session in a multiple-session application requires an independent connection to the Enterprise Access products or DBMS server. When creating multiple-session applications, keep the following points in mind:
• In a multi-session application, an application can encounter deadlock against itself. For example, one session may attempt to update a table that was locked by another session.
• An application can also lock itself out in an undetectable manner. For example, if a table is updated in a transaction in one session and then selected from in another transaction in a second session, the second session waits indefinitely.
• For sessions connected to Ingres databases, be sure that the server parameter connect_limit is large enough to accommodate the number of sessions required by the application.
Last modified date: 04/03/2024