Le lundi 15 mai 2006 à 14:21 -0300, Luiz Americo a écrit : > Editing in the TDbGrid does not call the sqlite database, so > SqlitereturnString has no meaning. > SqliteReturnString only has a meaning after calling ExecSql, Open, > CreateTable etc functions. > > TSqliteDataset does not handle unique, not null constraints of all > fields automatically. The programmer must do yourself using OnValidate > event.
ah... it seemed to me that SqliteReturnString allways return the good value, i.e 'SQLITE_CONSTRAINTS' when there's constraints problems, SQLITE_OK when all right and so on... I understood it as if TSqliteDataset only received the error message from the sqlite3 engine, because the database file contains indices with unique constraints. So your advice is NOT to check SqliteReturnString when editing in the dbgrid, because it can return a wrong value? > Try the fpc svn version of sqlite3ds or the one found at > http://www.geocities.com/camara_luiz/sqlite4fpc/index.html. It has more > verbose messages among other improvements. I just updated both fpc svn and lazarus svn but I can't make them work together. I can compile lazarus, but impossible to install components because of units not found. Don't have time to fix it for the moment so I'll try to compile only the last sqlite3ds with fpc-2.0.2-0 and today's lazarus svn. should work. Thanks for your time, -- Thierry Andriamirado Site web: http://thierry.andriamirado.free.fr _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
