, February 05, 2001 4:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Speeding up database accesses
Whoops! Over my head! Where would I learn more about how to do this?
= Original Message from [EMAIL PROTECTED] at 2/05/01 4:27
pm
Write a connectionpool as a bean and give it the scope of application
Write a connectionpool as a bean and give it the scope of application.
-Original Message-
From: John Coonrod [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 4:19 PM
To: [EMAIL PROTECTED]
Subject: Speeding up database accesses
I would like to leave my oracle database
One possibility (altough a bad idea) is to stick it into your
session.
Another possibility is to create an object that has a static
variable for the Connection. Then provide methods to access it. Remember
that you need to make sure only one thing at a time is using the
While there are connection pools (I have not used them but others on the
list can point you to them), I find the easiest solution is a session
variable. Then make a function you can call with the session and db
connection info. The function checks the session for the DB varaible. If
it's not
Whoops! Over my head! Where would I learn more about how to do this?
= Original Message from [EMAIL PROTECTED] at 2/05/01 4:27
pm
Write a connectionpool as a bean and give it the scope of application.
-
To unsubscribe,
up database accesses
Whoops! Over my head! Where would I learn more about how to do this?
= Original Message from [EMAIL PROTECTED] at 2/05/01 4:27
pm
Write a connectionpool as a bean and give it the scope of application
Sure it possible. For the page for example, at least you can do is
use
---
%@ page import="java.sql.*" %
%!
Connection conn;
PreparedStatement stmt;
%
%!
public void jspInit() {
try {
String url
Why is it a bad idea to use a session variable?
-Original Message-
From: Randy Layman [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 3:52 PM
To: [EMAIL PROTECTED]
Subject: RE: Speeding up database accesses
One possibility (altough a bad idea) is to stick
variable?
-Original Message-
From: Randy Layman [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 3:52 PM
To: [EMAIL PROTECTED]
Subject: RE: Speeding up database accesses
One possibility (altough a bad idea) is to stick it into your
session.
Another
[mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 4:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Speeding up database accesses
For one reason you are going to have a connection dedicated
to that session even if it isn't using it, so you will
have one connection per session when you really
Just stick with that example I gave you. OR use PoolMan. It's great
manager!
By initializing DB connections on init(), do the job.
Original Message
On 2/5/01, 1:42:21 PM, "Steve Ruby" [EMAIL PROTECTED] wrote
regarding Re: Speeding up database accesses:
For one reason you
ot;Randy Layman" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 05, 2001 1:13 PM
Subject: RE: Speeding up database accesses
I hate it when other people beat me to the responses
Basically, yes. Another reason is that some of the JDBC drivers
taht I have work
12 matches
Mail list logo
