[kexi] [Bug 345210] New: next unique key number not generated when saving new data-populated record

[Ian Balchin]

https://bugs.kde.org/show_bug.cgi?id=345210

            Bug ID: 345210
           Summary: next unique key number not generated when saving new
                    data-populated record
           Product: kexi
           Version: 2.9.0
          Platform: Mint (Ubuntu based)
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Forms
          Assignee: kexi-bugs at kde.org
          Reporter: inksi at fables.co.za
                CC: adam at piggz.co.uk, inksi at fables.co.za

I normally open a new record and populate it with data. Then I either save,
move to another record using the < > arrows (or a record number in the search
box). or create another new record. With such an action the unique key number
is generated and entered into the field.

This does not occur now. The new record cannot be saved because the key field
is perceived as empty.

Reproducible: Always

Steps to Reproduce:
1. Open data entry form
2. click on 'new record' + 
3. enter some data
4. click 'Save Record' button
5. OR click on 'New Record' or the 'Go to previous record' <

Actual Results:  
Warning:

Record changing failed.
You can correct data in this record or use "Cancel record changes" function.

Primary key's field "hash" cannot be empty.
SQL statement: UPDATE books SET 
Server result: 0


Expected Results:  
Record should be allocated next sequential key number

Using postgresql 8.4

To work around
1. open new record, enter a couple of characters and then CLICK 'Cancel Record
Changes'
THEN EITHER
2. move one record back
3. move one record forward which will now be numbered
OR
4. click 'Save Record'
OR
5. click 'New Record'+

ie. a new key can only be allocated when saving a record which has been
subjected to 'Cancel Record Changes'.

Saving a freshly created empty unedited record will not generate the new key.
various editing gymnastics are needed to enable this.

Effectively you must ensure that the new record is numbered before entering in
data.

-- 
You are receiving this mail because:
You are the assignee for the bug.