sqlite v2 edit row doesn't work after 1.8.8

[Former user]

Originally reported on Google Code with ID 91

What steps will reproduce the problem?
1. Create table with two colums and some data
2. Click edit row in that table
3. Click Save Changes

What is the expected output? What do you see instead?
To save that row with new data, instead I get  an error message "error:not an arror"

What version of the product are you using? On what operating system?
SQLite version: 2.8.17
SQLite extension: SQLiteDatabase
PHP version: 5.3.3-7+squeeze3

Please provide any additional information below.
Managing SQLite version 3 databases works as it should and I narrowed the bug to phpliteadmin
v.1-8-9 and higher, v 1-8-8 and below works great

Reported by petar.koretic on 2012-02-25 14:12:44

[Former user]

``` I wonder if the problem is in the data. If your data contained dots or nonstandard characters like @ or ( or ) or # it might be the same problem that I experienced in updating a row and entering such characters. This also ends in "error:not an error" and not entering the typed stuff in the row.

I reported this in problem 84. I also showed there a temporary fix in line 2025 which worked for me. Good luck.

Eke van Batenburg ```

Reported by `ekevanbatenburg` on 2012-03-15 00:36:19

[Former user]

``` i tested with simplest example which contained 'test' word both for table name and row data The problem exist only from mentioned versions above...so there is a obvious problem ```

Reported by `petar.koretic` on 2012-03-15 16:20:58

[Former user]

``` there is an issue with quotes in sqlite v2 version interface of sqliteadmin. try to add an 'TEST' text rather than TEST (w/o quotes), and see what happened. if it works fine, than you can use patched version from 75th issue by "crazy4.." guy ))

http://code.google.com/p/phpliteadmin/issues/detail?id=75 ```

Reported by `[e-mail]` on 2012-04-09 11:53:58

[Former user]

``` THIS WAS JUST AN EXAMPLE! It doesn't work, everything works just fine until v1.8.9 I know that you are trying to help but you aren't helping! I doesn't work with TEST, 'TEST', "TEST" or anything like that

Like i've said, if you test v 1.8.8 all of this will work, in 1.8.9 and later it wont ```

Reported by `petar.koretic` on 2012-05-25 12:06:23

[Dane Iracleous]

``` This seems like a serious issue, but I currently don't have access to a server with the versions required to reproduce the issue. If someone with the ability to diagnose or fix the problem and the correct versions could take this on, I would really appreciate it. ```

Reported by `diracleo` on 2012-06-02 08:19:50 - Status changed: `Accepted` - Labels added: Priority-High - Labels removed: Priority-Medium

[Christopher Kramer]

``` I just tried to reproduce this bug, but did not manage to in 1.9.2. Are you trying to edit the value of a row or the name of a column? I get this error when editing columns, i.e. changing column name or type. But this is buggy anyway (see issue #12).

I tried this using: phpLiteAdmin: 1.9.2 and 1.9.3 (from SVN) SQLite version: 2.8.17 SQLite extension [?]: SQLiteDatabase PHP version: 5.3.8

I could reproduce the error in 1.9.1, but I guess you are already using 1.9.2 as [e-mail] correctly referred you to issue #75, right? I even could not reproduce it in 1.9.1 using "Test" as the new value.

Please try version 1.9.2 if you have not done yet. If you still get this error, please give a detailed example: - please upload your example database file to the bugtracker - let us know which row you try to change and which new value you try to set to which column ```

Reported by `crazy4chrissi` on 2012-06-02 20:11:34

[Christopher Kramer]

Unfortunately we did not get any further information regarding this issue.
I just tried again to reproduce this in 1.8.9. It occurred with stuff like test, but
not with "test" (in double quotes). Clearly 1.8.9 is not escaping strings correctly
for sqlite v2 (issue #94). But this is fixed since 1.9.2.

The only possibility that "test" does not work I can imagine: If the column is a non-Text
column with a (primary key) index and you try inserting a string. SQLite has weak typing,
but not on indexes.

I highly doubt this issue is still in current versions, so I am closing it.

If you or anybody else sees this issue in 1.9.2 or the current development (SVN) version,
please comment on this issue giving more details and I will re-open it. Thanks.

Reported by crazy4chrissi on 2012-10-22 21:31:27 - Status changed: Fixed

[Christopher Kramer]

Sorry, I did not mean issue 94 but issue #75.

Reported by crazy4chrissi on 2012-10-22 21:32:46

[Former user]

I can also confirm this is fixed in 1.9.2.

Reported by petar.koretic on 2012-10-23 08:35:31

[Christopher Kramer]

Thanks for confirming the fix.

Reported by crazy4chrissi on 2012-10-23 10:11:57