Page 1 of 1

Bug in Edit Data > Delete

Posted: 03.09.2007, 22:18
by thorsten
The function in the subject deletes *all* rows in a table - not just the one that is selected

Posted: 03.09.2007, 22:26
by thorsten
thorsten wrote:The function in the subject deletes *all* rows in a table - not just the one that is selected
Actually after executing "delete" it shows only the one row that I selected "gone". But when I go to the fields view everything is deleted. Baaaaaaaaaaad

Posted: 04.09.2007, 07:32
by Orbmu2k
I can not confirm this bug.

Posted: 04.09.2007, 09:20
by thorsten
I could reproduce it on two different XP SP2 machines with the latest Beta.

But instead of this I found another weirdness:

Create new database called test.s3db, create a table called test, add two fields called test1 and test2 of type text (do not check anything else).

Select table test1 in the explorer view:
NEW > Tables > test > Fields > test1, select the "Edit Data" tab, select table test from the drop down menu ("Table:"); double click the fields for test1 and then test2, enter in the "Edit Memo" editor A (for test1) and then B for test 2,

Click on the plus ("+") sign and enter another data set (row) with C and D.
Close SQLiteAdministrator and open the database again (or just go to the table in the explorrer view and then back):

Now you see instead of
test1 test2
A B
C D

test1 test2
A D
C D

Can anyone reproduce this funny behaviour?

Posted: 04.09.2007, 10:06
by thorsten
I can offer you to make a "video" of this issue or we'll do some kind of a remote session(MSN messenger offers that, I think, or something like www.copilot.com which is free for two minutes).

The "misbehaviour" of the application is so apparent that I cannot think of me doing something wrong.

Posted: 04.09.2007, 11:44
by Orbmu2k
yeah i think i know whats going wrong...

on a table without a primary key the dataset does not know what row it have to delete.

i think this issue is related to zeoslib ... it must user the "rowid" feature if there is no primary /unique key available.


for workaround this bug you simply have to add a autoincrement primary key field to each table ;-)

Posted: 04.09.2007, 12:41
by thorsten
Okay, with primary key it works.