Yes, just changing the DLL is safe. I believe the default DLL might need to be compiled with SQLITE_ENABLE_COLUMN_METADATA. I replace the sqlite3.dll in Python all the time to keep it up-to-date with the latest head.
>-----Original Message----- >From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- >boun...@sqlite.org] On Behalf Of Richard Hipp >Sent: Wednesday, 15 January, 2014 11:55 >To: General Discussion of SQLite Database >Subject: Re: [sqlite] SqlAlchemy 0.9 release note complaint > >On Wed, Jan 15, 2014 at 1:53 PM, big stone <stonebi...@gmail.com> wrote: > >> Ok, >> >> The problem is fixed starting SQLite 3.7.16, >> But Python 3.3 series (up to 3.3.3) seems to be shipped with the very >old >> SQLite 3.7.12, by default. >> >> Is there a simple trick to "upgrade" SQLite3 version used by Python >(under >> windows) ? >> Just changing the sqlite3.dll is safe ? >> > >That's really a question for the Python people, but my guess is that >changing the sqlite3.dll would be safe. > > > >-- >D. Richard Hipp >d...@sqlite.org >_______________________________________________ >sqlite-users mailing list >sqlite-users@sqlite.org >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
