important "patterns")
/max
/max
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
Andersen
Sent: Wednesday, August 30, 2006 3:01 PM
To: Christian Bauer; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
hl
Andersen
Sent: Wednesday, August 30, 2006 3:01 PM
To: Christian Bauer; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
The question was simply whether exposing the
Work/command APIs justify removal of the connection() method from the
perspective of using it f
; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
The question was simply whether exposing the
Work/command APIs justify removal of the connection() method from the
perspective of using it for direct JDBC work. I do not know that
answer
to that
Then we need @bad... ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl
Andersen
Sent: Wednesday, August 30, 2006 3:01 PM
To: Christian Bauer; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
>> The questi
The question was simply whether exposing the
Work/command APIs justify removal of the connection() method from the
perspective of using it for direct JDBC work. I do not know that answer
to that. Unfortunately, I suspect it does not and that we will need to
keep connection() around; but one ca
t one can dream.
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 12:08 PM
To: Steve Ebersole
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
Session s = ...;
Connection c = s.connection();
PS stmnt = c.prepareStatement( ... );
RS rs = stm
On Aug 30, 2006, at 9:39 PM, Steve Ebersole wrote:
The question was simply whether exposing the
Work/command APIs justify removal of the connection() method from the
perspective of using it for direct JDBC work. I do not know that
answer
to that. Unfortunately, I suspect it does not and tha
answer
to that. Unfortunately, I suspect it does not and that we will need to
keep connection() around; but one can dream.
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 12:08 PM
To: Steve Ebersole
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Conn
ion.doWork(
new Work() {
public void performWork(Workspace workspace) {
c[0] = workspace.getConnection();
}
}
);
/max
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 9:09 AM
To: Steve Ebersole
Cc: hibernate-dev@lists.jbos
re the arguments *against* session.connection() if you do the
proxying you
are suggesting ?
/max
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 2:30 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
Since the intent
, August 30, 2006 2:30 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
Since the intention is to provide a safer execution for the user then
+1,
but if you are going to do this then i guess session.connection() will
still be ok
since it will ju
explicitly
circumvented...
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 9:09 AM
To: Steve Ebersole
Cc: hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
> However, removing that connection() method does additionally create an
&
re the arguments *against* session.connection() if you do the
proxying you
are suggesting ?
/max
-Original Message-
From: Max Andersen
Sent: Wednesday, August 30, 2006 2:30 AM
To: Steve Ebersole; hibernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
Since the intent
ernate-dev@lists.jboss.org
Subject: Re: [hibernate-dev] Connection proxying
Since the intention is to provide a safer execution for the user then
+1,
but if you are going to do this then i guess session.connection() will
still be ok
since it will just be proxied.
btw. your example is a bit simpli
Since the intention is to provide a safer execution for the user then +1,
but if you are going to do this then i guess session.connection() will
still be ok
since it will just be proxied.
btw. your example is a bit simplified since when hibernate runs inside an
appserver
the user will norma
15 matches
Mail list logo
