You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the comments in fossilpy, I can assure you that there is little value in trying to use SQL directly, although Fossil has an 'sql' command that can be useful. And there are code examples that will enable you to access pretty much any level of detail you like from a Fossil repo.
Dan Shearer
The text was updated successfully, but these errors were encountered:
I knew this library. I think it has not been updated for a long time, while it becomes active now. Since using pure Python to read the repo is simple, why bother to write the cffi/ctypes?
It's true that it wasn't updated for about 6 years, as i was out with severe chronic RSI and nobody else picked up the ball. It's now seeing a revival, though, and has been updated to read fossil repos created since its introduction of SHA3 hashes.
If you're only reading from the existing DB schema, instead of accessing the low-level SCM data, using a C library would likely not be worth the effort. If you want to extract file content from the db, though, it cannot be done without fossil/libfossil-level support because the file contents are stored using a combination of zlib and delta compression. Trying to read them directly from the db, without the appropriate decoder algos, will just lead to useless garbage.
Hello Gumblex,
You might like to look at calling libfossil from Python to achieve your goals? https://fossil.wanderinghorse.net/r/libfossil/ has scripting bindings, although not yet for Python.
Looking at the comments in fossilpy, I can assure you that there is little value in trying to use SQL directly, although Fossil has an 'sql' command that can be useful. And there are code examples that will enable you to access pretty much any level of detail you like from a Fossil repo.
Dan Shearer
The text was updated successfully, but these errors were encountered: