| Summary: | BASE: FIREBIRD: Auto-value is incremented when input was aborted by Firebird database due to erroneous input | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | simon.i |
| Component: | Base | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED NOTABUG | ||
| Severity: | minor | CC: | lionel, miguelangelrv, robert, xiscofauli |
| Priority: | medium | ||
| Version: | 6.2.4.2 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 51780 | ||
| Attachments: | See "Table1" in the attached database - not NULL for field Surname | ||
|
Description
simon.i
2019-06-16 14:09:07 UTC
Created attachment 152232 [details]
See "Table1" in the attached database - not NULL for field Surname
The buggy behaviour isn't a buggy behaviour of the form. It could also be reproduced in a table.
Try to insert content in the table "Table1" without filling "Surname" with content. It will fail with an error from Firebird - but the counter for "ID" will count everytime I try to submit the data.
I`m not sure it is a bug, Firebird use transactions, Some explanation http://docs.openlinksw.com/virtuoso/identity/. On the other hand, if I'm not wrong, basic use of auto increment columns are for to have a primary key for the table, so records have unique IDs on the table. FWIW, I seem to recall that the same behaviour occurs when working with postgresql and an autovalue field. I also seem to recall reporting this at the time, and it being deemed not a bug...(but I can't find the bug report at the moment). autoincrement fields have unique values, but are not necessarily strictly sequential. That is indeed so in several different DMBS. It is kinda hard (not sure even possible) to ensure the values are strictly sequential, if one allows transactions (that can be cancelled...) and/or concurrent inserts. |