thankyou, for all your valuable responces.
From: Dave Newton <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List"
To: Struts Users Mailing List
Subject: Re: [OT] Re: design question
Date: Tue, 31 Jan 2006 10:13:24 -0500
fea jabi wrote:
> you have mentioned that
&
fea jabi wrote:
> you have mentioned that
>
> "You're going to have an object in memory no matter what"
>
> If we are using Resultset how/when is the Object getting created? I
> was under the impression that it will get the data directly from the DB.
Uh... a ResultSet is an object.
>> You're going
somewhere that if this approach is used then we'll be
breaking the MVC architecture.
any reference links for this?
Thanks.
From: Dave Newton <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List"
To: Struts Users Mailing List
Subject: Re: [OT] Re: design question
D
fea jabi wrote:
> But as I mentioned earliar I am creating an object which I am planning
> to instanciate for each row of data. When I told about this to my team
> they were concerned about the objects being in memory and advised to
> use the resultset directly. In the sessionbean probably we can c
Thanks for your responses.
I am currently not interacting with DB. Will ofcourse be soon.
But as I mentioned earliar I am creating an object which I am planning to
instanciate for each row of data. When I told about this to my team they
were concerned about the objects being in memory and advi
Dave Newton replied:
> In general, I have pretty strong feelings against using "raw"
> ResultSets despite the overhead of copying data... anything
> other than raw JDBC will see the same behavior whether it's a
> full ORM or something as simple as a RowSetDynaClass (from
> Jakarta BeanUtils).
6 matches
Mail list logo
