You need an identifier to update an object, which usually corresponds to
a PK in your database. When the identifier is not present or does not
correspond to a persisted entry, you probably want to create.
hth,
Manos
Andrew Tomaka wrote:
Hey all,
The following is pretty hard to understan
I agree fully, but, unfortunately, I can't do a whole lot about it.
The databases were set up before I started on the project and I guess
the DBA was pretty hard nosed about changing from how he wanted it.
Oh well.
~ Andrew Tomaka
On 7/27/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> On
On 7/27/05, Andrew Tomaka <[EMAIL PROTECTED]> wrote:
> I realized the
> problem was actually a bit more complex than I was making it. The
> database table I am editing requires two primary keys to make an entry
> unique (I'm a firm believer in a single PRImary key, but it wasn't my
> choice).
A
I really like your Javascript solution, Kevin. However, I realized the
problem was actually a bit more complex than I was making it. The
database table I am editing requires two primary keys to make an entry
unique (I'm a firm believer in a single PRImary key, but it wasn't my
choice). One of the
Andrew-
At some point, you're probably going to need to know which records
have been changed and which ones haven't. If the dataset isn't too
big, you could add a collection (java.util.List, etc.) of records that
you are displaying, and store it either as a formbean attribute or in
the session. If
Just a suggestion,
If you do the rows by javascript you can add a hidden field which can have a
value (eg 0 for update 1 for creation)
Regards,
Kevin
- Original Message -
From: "Andrew Tomaka" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List"
Sent: Wednesday, July 27, 2005 9:47 PM
6 matches
Mail list logo
