Issue Details (XML | Word | Printable)

Key: CORE-903
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Eduardo
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Update Field update / result Updated

Created: 18/Aug/06 01:54 PM   Updated: 20/Apr/11 09:19 AM
Component/s: API / Client Library
Affects Version/s: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.5.0, 1.5.1, 1.5.2, 1.5.3, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.0.4, 2.1.1
Fix Version/s: 2.5 Beta 1

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Relate
 

Target: 2.5.0


 Description  « Hide
UPDATE CONTA_AMB_PROCED
  SET CEVH=(SELECT (((CEVH+CEVL) * CEQT) * (PNDA / 100)) FROM PROFISSIONAL_CONVENIO WHERE PNCV=:CVDD AND PNPR=(SELECT CPPR FROM CONTA_AMB_PROCED_MESTRE WHERE CPAM=CEAM AND CPCD=CECP)), CEVL=(SELECT (((CEVH+CEVL) * CEQT) * ((100-PNDA) / 100)) FROM PROFISSIONAL_CONVENIO WHERE PNCV=:CVDD AND PNPR=(SELECT CPPR FROM CONTA_AMB_PROCED_MESTRE WHERE CPAM=CEAM AND CPCD=CECP))
  WHERE CEAM=(SELECT F2AM FROM FATURA_DETALHE_AMB WHERE F2F1=:FAT AND F2AM=CEAM) AND CEVC=0;

First Set CEVH = ok
Second Set CEVL = BUG

Second CEVL = 1? CEVH(UPDATED) + CEVL

Normal CEVL = (CEVL + CEVL) NO UPDATED

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Adriano dos Santos Fernandes added a comment - 18/Aug/06 02:33 PM
Eduardo, the information that you provided is not sufficient to understant.

What is incorrect?

Could you attach a backup?

Eduardo added a comment - 18/Aug/06 04:09 PM
my english is very bad, portuguese vension translate to english

-> Estou tentando fazer um update em uma tabela CONTA_AMB_PROCED aproveitando os valores do campo CEVH e CEVL, com o calculo mensionado acima, o calculo para o CEVH esta gravando corratamente porem o do CEVL esta calculando j? com o primeiro que e do CEVH o que n?o poderia acontecer, pois ainda n?o comitei o registro, estou utilizando esta opera??o em uma SP.

Obrigado

Adriano dos Santos Fernandes added a comment - 18/Aug/06 04:30 PM
The problem (one updated field should continue with old value when evaluating others assignments) is already fixed in the tree but is disabled.

It's scheduled to enable for V3.0 AFAIK.

Eduardo added a comment - 18/Aug/06 06:41 PM
only 3.0 :(, trank

Dmitry Yemanov added a comment - 25/Aug/06 05:50 AM
Many people rely on the existing behaviour, so we cannot change it quickly. This will be addressed in the next major version, probably along with some backward compatibility option.

Eugenk Konkov added a comment - 13/Nov/08 02:04 PM
I have installed new instance of 2.0.3 Firebird
Is there some options on server side to not use this existing behaviour?
I do not need new value of field before it will updated

Dmitry Yemanov added a comment - 14/Nov/08 05:04 AM
No, there's no workaround, sorry. The proper behavior is implemented in v2.5 only.

Pavel Cisar added a comment - 23/Feb/11 01:03 PM
Dmitry, could you please adjust the Fix version according to your plans? If it should appear in 3.0, the current Fix version: 2.5 Beta 1 doesn't look right to me.

Dmitry Yemanov added a comment - 23/Feb/11 01:13 PM
Pavel, it was fixed (or implemented, if you wish) in v2.5, see my last comment here.

Pavel Cisar added a comment - 23/Feb/11 01:43 PM
Dmitry, I can read :) But Adriano explicitly stated that although it was implemented in 2.5 tree, it's disabled (hence not effective in 2.5 binary) and scheduled to be enabled in 3.0. So, from QA POV we can't create test for this issue against 2.5 and close the ticket until you enable the fix in some future release, and therefore it makes sense to assign Fix for version accordingly to your real plans. In fact, this ticket should be reopened (and sub-task added) as you personally hinted that this issue would need further development (backward compatibility option). Or am I completely wrong?

Dmitry Yemanov added a comment - 23/Feb/11 01:57 PM
Adriano said that in 2006, there wasn't v2.5 that time :-) In fact, it was implemented (and disabled) during the v2.1 development, and it was enabled and surfaced in v2.5. The corresponding backward compatibility option is OldSetClauseSemantics in firebird.conf.

Pavel Cisar added a comment - 23/Feb/11 02:37 PM
Ouch, you're right. Now I remember I saw it in release notes :-) I've visited so many old tickets recently during general clean up that my general sense of development chronology is completely messed up and my recall paths are blurry at best. Thanks for clarification.

Pavel Cisar added a comment - 20/Apr/11 09:19 AM
QA test added.