[EMAIL PROTECTED] writes: >> Profiling revealed that version 3.4.2 seems to have some kind of problem >> with the DB if created with version 3.3.8 of the library. These are the >> first lines of the profiled data on an (despite sqlite) basically idle >> system: >> >> samples % app name symbol name >> 574 7.1616 libsqlite3.so.0.8.6 sqlite3VdbeExec >> 485 6.0512 libsqlite3.so.0.8.6 __i686.get_pc_thunk.bx >> 315 3.9301 libsqlite3.so.0.8.6 sqlite3VdbeSerialType >> 265 3.3063 libsqlite3.so.0.8.6 sqlite3VdbeSerialPut
> The database file format has not changed. You are the first > person to report any similar problems. Are you *certain* that > is the database upgrade that is causing your problem? Well, after profiling I stopped my application, moved the DB away and restarted. Then the problem went away. Also, after upgrading Sqlite my application was restarted, so I do not any reason to fail. Hmm... Sqlite 3.3.8 was the version as it is available on SuSE SLES10, while the updated version is the unpatched 3.4.2. Maybe I should go check the SuSE patches... /holger ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
