Bug 145900 - Firebird: copy records will copy row with max value AutoValue primarykey instead of inserted value before refreshing row
Summary: Firebird: copy records will copy row with max value AutoValue primarykey inst...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Firebird-Default
  Show dependency treegraph
 
Reported: 2021-11-26 13:40 UTC by mhonline
Modified: 2023-04-30 08:09 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
example (113.80 KB, image/jpeg)
2021-11-26 13:41 UTC, mhonline
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mhonline 2021-11-26 13:40:15 UTC
Description:
when using the dragdrop-feature within tableview, 
the copying is working, but displayed is a wrong one
until the view is closed an reopened.
This happens within HSQL-ODB aswell as in FB-ODB

Steps to Reproduce:
1.open any FB-table in table-view
2.select a record for being copied
3.drop it to the "+"-sign

Actual Results:
wrong record is shown
but right record stored

Expected Results:
show right record after copying


Reproducible: Always


User Profile Reset: No



Additional Info:
- - -
Comment 1 mhonline 2021-11-26 13:41:25 UTC
Created attachment 176524 [details]
example
Comment 2 mhonline 2021-11-26 14:00:35 UTC
oops - liked to edit my bugentry,as I mixed my test-files, but don't know how. 
So: This works fine with HSQL-odb, only FB-odb is faulty

mh
Comment 3 Robert Großkopf 2021-11-27 11:03:04 UTC
Have tested this with internal Firebird. Took a table with autovalue for primary key. Will work as expected if I won't change a value for a primary key to a number, which is bigger than the next inserted ID.

If I set the PK of one row to '222' and next inserted ID will be '9' it will show the row with PK 222 instead of the inserted content. You have to refresh the table to show the inserted value.

All tested with LO 7.2.3.2 on OpenSUSE 15.2 64bit rpm Linux.

Could be this bug has reported before - will have a look.