search

BugsBiteBugs / sqlitepersistentobjects

Automatically exported from code.google.com/p/sqlitepersistentobjects
0 stars 0 forks source link

SQLITE_RANGE Error in SQLitePersistentObject's save #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The code in save can end up binding to more columns than exist due to this 
check:

            if (theProperty == nil)
            {
                sqlError = sqlite3_bind_null(stmt, colIndex++);

The property may be nil, however the object may be on that facilitates a cross 
reference -- and 
thus won't ever use a column (as one wasn't created for it in checkTable).

Original issue reported on code.google.com by stepwh...@gmail.com on 16 Nov 2008 at 4:32

GoogleCodeExporter commented 9 years ago 
So, if you remove the check, does that solve the problem ?

Original comment by mnemonic...@gmail.com on 4 Dec 2008 at 2:14

GoogleCodeExporter commented 9 years ago 
This is a duplicate, fix for it was submitted tonight.

Original comment by jeff.lam...@gmail.com on 19 Feb 2009 at 1:13