stricted/patterns/DataAccessObject
> .html
>
> cheers,
> nicolas b.
>
>
>
> -Original Message-
> From: Ritter, Steve [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 6:41 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Where do YOU put
PM
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
Ryan, you should really read the J2EE blueprints on DAO. It covers
everything you need to know.
Search aroun javasoft.com for the blueprints (they are documents, not
software).
--Steve
-Original Message-
Fr
your
classes to the underlying database schema. No more code changes when
the DBA's change the column names, etc!
-Original Message-From: Ryan Cornia
[mailto:[EMAIL PROTECTED]]Sent: Thursday, July 19, 2001
00:36To: [EMAIL PROTECTED]Subject: RE:
Where do YOU put JDBC calls?
Message-From: Ryan Cornia
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, July 18, 2001
6:56 AMTo: [EMAIL PROTECTED]Subject: Where
do YOU put JDBC calls?
I'm wondering what people are considering best practices for
JDBC calls?
I have been writing beans that wrap a database
:36 AM
To: [EMAIL PROTECTED]
Subject: RE: Where do YOU put JDBC calls?
>From my understanding then -
I would have my Business Object class that wraps the table, lets call it Address.
I would have a DAO object that is specific to that Business object for the JDBC calls,
lets call it Address
EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 9:39 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
This is a nice pattern, but I do not want my DAO to be responsible for
getting the connection. I need to use them in the web-tier (no EJBs) and
possibly also the middl
ly 18, 2001 8:56 AMTo:
[EMAIL PROTECTED]Subject: Where do YOU put JDBC
calls?I'm wondering what people are considering best practices
for JDBC calls?I have been writing beans that wrap a database table, and
include functions"select", "insert", "delete". These fu
w how.
mark
-Original Message-
From: Pathangi, Rao H. [mailto:[EMAIL PROTECTED]]
Sent: 18 July 2001 15:33
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
Mark
To handle this situation, I wrote a base class which has the connection
Object as a protected variable. Le
{
//close connection, unplug your DAO
}
}
Hope that helps
pathangi r
-Original Message-
From: Geddes, Mark (ANTS) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 9:23 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
ditto.
I am always reading that the
DataSource
and ensure that my DAO method obtains and closes the connection. Shoot me
down if you like.
Mark
-Original Message-
From: Pathangi, Rao H. [mailto:[EMAIL PROTECTED]]
Sent: 18 July 2001 15:18
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
Iam usi
anks
pathangi r
-Original Message-
From: Pathangi, Rao H.
Sent: Wednesday, July 18, 2001 9:18 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Where do YOU put JDBC calls?
Iam using the DAO(Data Access Object) design pattern for such Data access
situations. DAO is a layer of abstraction that
EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 8:56 AM
To: [EMAIL PROTECTED]
Subject: Where do YOU put JDBC calls?
I'm wondering what people are considering best practices for JDBC calls?
I have been writing beans that wrap a database table, and include functions
"select", "
Hello Ryan,
Wednesday, July 18, 2001, 5:55:46 PM, you wrote:
RC> I'm wondering what people are considering best practices for JDBC calls?
RC> I have been writing beans that wrap a database table, and include functions
"select", "insert", "delete". These functions either load the bean, insert t
I'm wondering what people are considering best practices for
JDBC calls?
I have been writing beans that wrap a database table, and
include functions "select", "insert", "delete". These functions either load the
bean, insert the bean values in the database, or delete the record from the
dat
14 matches
Mail list logo
