about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Schnitzer
Sent: vrijdag 3 mei 2002 8:02
To: [EMAIL PROTECTED]
Subject: Re: PreparedStatement vs Statement
The primary reason to use PreparedStatement has nothing to do with
performance.
When you
: Jeff Schnitzer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 03, 2002 11:32 AM
Subject: Re: PreparedStatement vs Statement
When you are building your query for a Statement:
String sql = SELECT * FROM theTable WHERE name = ' + name + ';
With PreparedStatement, you never need to worry
Performance will ofcourse play the major role in selecting
between the two.
I seriously doubt that.
- Correctness
- Stability
- Security
- Maintainability
Are IMO all much more crucial than raw speed.
Geert Van Damme
]] On Behalf Of Jeff Schnitzer
Sent: 03 May 2002 07:02
To: [EMAIL PROTECTED]
Subject: Re: PreparedStatement vs Statement
The primary reason to use PreparedStatement has nothing to do with
performance.
When you are building your query for a Statement:
String sql = SELECT * FROM theTable WHERE name
Can you explain these four points in terms of statements/preparedstatements
specially security ,stability , correctness ?
Ashwani
- Original Message -
From: Geert Van Damme [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 03, 2002 3:42 PM
Subject: Re: PreparedStatement vs
specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Ashwani Kalra
Sent: vrijdag 3 mei 2002 12:34
To: [EMAIL PROTECTED]
Subject: Re: PreparedStatement vs Statement
Can you explain these four points in terms of
statements/preparedstatements
specially security ,stability , correctness
: Re: PreparedStatement vs Statement
The difference between Statement and PreparedStatement is in the order of
nanoseconds. I'm sure it's less than 1 ms on normal hardware.
That means it would take 1000 requests to increase the processor time
with
1 second. I'd say that this is cheap ;-) I'm
My main point is that performance generally isn't that much an issue in
server side web development.
I cant believe this !!! . In out project we are trying hard to increase
throughput and response time/performance. These small-2 points add and
later create problems.
e.g. the
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 03, 2002 5:12 PM
Subject: Re: PreparedStatement vs Statement
My main point is that performance generally isn't that much an issue
in
server side web development.
I cant believe this !!! . In out project we are trying hard to increase
is there a considerable difference, if I create PreparedStatement instead of
Statement after i get my DB connection?
are there pitfalls i should be aware about (using PreparedStatement)?
kenny
===
To unsubscribe: mailto
]
Reply-To: A mailing list about Java Server Pages specification and
reference [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: PreparedStatement vs Statement
Date: Thu, 2 May 2002 14:41:20 -0400
is there a considerable difference, if I create PreparedStatement instead
of
Statement after i get my DB
/
~
- Original Message -
From: suresh kumar Durairaj [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 03, 2002 6:51 AM
Subject: Re: PreparedStatement vs Statement
Dear all,
From the DB Perspective,
use of Prepared statement reduces the memory usage
: lots.
With PreparedStatement, you never need to worry about escaping.
Jeff Schnitzer
[EMAIL PROTECTED]
-Original Message-
From: Ashwani Kalra [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 8:58 PM
To: [EMAIL PROTECTED]
Subject: Re: PreparedStatement vs Statement
Hi,
I
13 matches
Mail list logo
