I've opened a PR (https://github.com/doxygen/doxygen/pull/9992) and have updated the fix; if you try this before it's merged, you can build from https://github.com/abathur/doxygen/tree/fix_schema_version.
Also, I noticed while poking at the sqlite `.read` command: it's not for loading a database--it'll throw parse errors even on a well-formed db. I think it expects the file to contain either SQL or a command that will generate SQL. On Wed, Apr 19, 2023 at 10:40 PM Travis Everett <travis.a.ever...@gmail.com> wrote: > I have a project with some tests against the SQLite behavior. I needed to > dust it off a bit, but I was able to get it working at the major versions > between now and the last time I touched it (without seeing this issue > myself). > > I did notice some regressed behavior, mostly around some 2021 QCString > refactoring and have a commit fixing it. I'm curious if this happens to > work for you if you build from it: > https://github.com/abathur/doxygen/commit/6106b5119ba84a692dd7cdf1e91535cbd83ec070 > > > The line you're quoting for the parse error looks like data for the "meta" > table. Here's an example of what that looks like in a db from one of my > tests: > > sqlite> select * from meta; > doxygen_version = 1.9.7 > schema_version = 0.2.1 > generated_at = Wed Jan 2 1980 00:00:00 > generated_on = Wed Jan 2 1980 > project_name = ManualTest > project_number = 1.1.22 > project_brief = A quick idea about the purpose of the project > > and the statement binding the value for `schema_version` is one of the > ones I fixed. > > On Tue, Apr 18, 2023 at 12:30 PM Chad Cornwell <cornwell.c...@gmail.com> > wrote: > >> I compiled from source on centos 7 using the scl dev toolset 7 (if this >> matters) for doxygen 1.9.7 with the -Duse_sqlite3 flag on. >> >> I was able to successfully run doxygen on my code directory and did not >> see any error flags pop up relating to sqlite3 (or any at all) however when >> I try to open up the database using sqlite3 it responds to .tables with ' >> Errror: file is not a database' >> >> Additionally when I try to .read doxygen_sqlite3.db it gives the >> following error: >> Parse error near line 1: unrecognized token "18a592b71f" >> 18a592b71fc2*)0.2.1TueApr 18 2023 17:54:53Tue Apr 18 2023My Project >> 05acdd2d7 >> ^--- error here >> >> It seems as if the data is populated into the .db file but it is getting >> corrupted somehow along the way, any ideas on how to fix this? Thank you so >> much for your help! >> _______________________________________________ >> Doxygen-users mailing list >> Doxygen-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/doxygen-users >> >
_______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
