I don't think encode.c is part of sqlite3 - it certainly isn't relevant now sqlite has proper blob support. I suspect it got left in DBD::SQLite as a remnant of the previous version.
That same file is in the 3.0.6 source tarball on the sqlite.org website ( http://sqlite.org/sqlite-3.0.6.tar.gz ); I checked, and that file is identical to the copy in DBD-SQLite 1.05, except for the date stamp inside. That said, the original date stamp was from March or April of 2004, so it may not be used.
If what you are saying is true, that it's not part of SQLite 3, then it should be removed from the main SQLite 3 CVS tree, and source tarball.
For that matter, there should be an investigation in case any other files in there should be dropped too. Dropping unused-and-not-to-be-used code is good prior to a 'generally available' release, cutting the disk/ram footprint down.
What say you, Richard?
-- Darren Duncan
