my option is
a) and it works far better than hibernate or ibatis :-)
as for other options:
b) can't happen, because you don't code sql in jsp if you code struts :-)
c) ah well, same as a) isn't it?
d) can't happen, there are no perfect applications, only changing
applications or dead applications
Mailing List
cc
Subject
[slightly OT] Prince of Struts questions his database maintenance strategy
Hi folks
This is for those of us not using Hibernate or iBatisthose still using
JDBC or DBCP.
You've spent 2 months (a blink in the eye of eternity really) creating
your killer St
ist
Subject: Re: [slightly OT] Prince of Struts questions his database
maintenance strategy
Date: Mon, 24 Oct 2005 21:13:47 -0600
In spite of being one of "the others" who use iBATIS, I go with (a)
and script the database changes.
Larry
On 10/24/05, Murray Collingwood <[EMAIL PROTECTED]&g
In spite of being one of "the others" who use iBATIS, I go with (a)
and script the database changes.
Larry
On 10/24/05, Murray Collingwood <[EMAIL PROTECTED]> wrote:
> Hi folks
>
> This is for those of us not using Hibernate or iBatisthose still using
> JDBC or DBCP.
>
> You've spent 2 month
Hi folks
This is for those of us not using Hibernate or iBatisthose still using JDBC
or DBCP.
You've spent 2 months (a blink in the eye of eternity really) creating your
killer Struts
app. It launched without any problems (you know it's a fairy tale now) and you
were
hailed by many fell
5 matches
Mail list logo
