Issue Details (XML | Word | Printable)

Key: CORE-5113
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: tvr
Votes: 0
Watchers: 4
Operations

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

incorrect update of newly added column from older connection - column value is changed to null even if not included in update statement

Created: 17/Feb/16 10:55 AM   Updated: 17/Feb/16 10:55 AM
Component/s: Engine
Affects Version/s: 2.5.5
Fix Version/s: None

Environment: Windows 7 professional 64b, FB 2.5.5.26952 64b installed as classic (tested on 2.5.2.26539 32b with same result too)

QA Status: No test


 Description  « Hide
I tried it with to isql instances:
1. Open first instance
2. Open second instance, add new column to table and change its value
3. Return to first instance and change value of some old column. By this is value in new column is set to NULL, even though new column is not mentioned in update statement.

Steps to reproduce:
Create test table and fill one row:
CREATE TABLE FBTEST
(
  CONE VARCHAR(10)
);

FIRST ISQL CONNECTION:
SQL> select * from fbtest; commit;

CONE
==========
kuktest


SECOND ISQL CONNECTION:
SQL> select * from fbtest; commit;

CONE
==========
kuktest

SQL> alter table fbtest add ctwo varchar(10); commit;
SQL> update fbtest set cone='kuk1', ctwo='kuk2'; commit;
SQL> select * from fbtest; commit;

CONE CTWO
========== ==========
kuk1 kuk2


FIRST ISQL CONNECTION:
SQL> update fbtest set cone='hi'; commit;
SQL>


SECOND ISQL CONNECTION:
SQL> select * from fbtest; commit;

CONE CTWO
========== ==========
hi <null> ---------------------------> expected to see hi kuk2

SQL>

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no entries against this issue.