Hi,
> "Cook, Thomas" wrote:
> Sorry, I'm getting a bit out of my depth now;
> I've never seen the problem, and I don't know the
> server internals well enough to comment.
> Someone else wanna go?
Just my US$0.02:
Log says:
[JAWS] Create command executing: INSERT INTO music_cd
(cd_artist,cd_notes,cd_type,cd_title,cd_id) VALUES (?,?,?,?,?)
[JAWS] Set parameter: idx=1, jdbcType=VARCHAR, value=NULL
[JAWS] Set parameter: idx=2, jdbcType=VARCHAR, value=NULL
[JAWS] Set parameter: idx=3, jdbcType=VARCHAR, value=NULL
[JAWS] Set parameter: idx=4, jdbcType=VARCHAR, value=NULL
[JAWS] Set parameter: idx=5, jdbcType=CHAR, value=1
[JAWS] Rows affected = 1
[JAWS] Store command executing: UPDATE music_cd SET
cd_artist=?,cd_notes=?,cd_type=?,cd_title=? WHERE cd_id=?
[JAWS] Set parameter: idx=1, jdbcType=VARCHAR, value=Koopman
[JAWS] Set parameter: idx=2, jdbcType=VARCHAR, value=Incl. Toccata & Fugue in D minor
[JAWS] Set parameter: idx=3, jdbcType=VARCHAR, value=classical, organ
[JAWS] Set parameter: idx=4, jdbcType=VARCHAR, value=Great Organ Works/Bach JS
[JAWS] Set parameter: idx=5, jdbcType=CHAR, value=1
[JAWS] Rows affected = 0
Note that the UPDATE SQL statement affects no rows.
My guess is that a SELECT for cd_id=1 would also return
no rows at this place.
Why?
Probably transaction isolation:
Isolation means that other users (really transactions)
cannot see the new row created with the CREATE
statement until the transaction is committed.
My guess is that the database mistakes the UPDATE
statement as coming from another transaction.
How are the transactional attributes defined?
How are the datasources defined?
If possible, please respond in text.
I hate HTML mail.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
