-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database files: sqlite, dbf etc? #27
Comments
Hi, it depends a bit what the usage is. The main usage of fq it to provide detailed access to a binary format so formats that have "user facing" (rows and columns etc) format that is different from how it's actually encoded (indexes and various compact value encodings etc) might decode to something a user would not expect. Have a look at #25 where i describe issue and possible solutions to it. BTW have you looked at https://github.com/neilotoole/sq? is that more close to want your looking for? |
I mean access of raw structures. Yep it is more close to real data for simpler/older databases like dbf (my common problem: what is charset?) and can be more tricky for eg sqlite or leveldb. |
Ok! then a fq decoder could be a good fit i think. Is it something you would be interested to work on? I wonder how hard it would be to have some per format plumbing in jq that traverses the raw structure and output rows etc. Actually jq:s standard library has some SQL-like support already :) |
See sqlite3.{go,jq} for TODO Related to #27
Hey, got a bit curious how btree traversing in jq could work so had to just try. Very much work in progress and does not support page overflow yet so probably only works with tables with small rows. Feel free to work on it if you want or if you have any data modeling and naming suggestions. With this you can do this:
|
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
Made some progress but still needs work. This works now, i call it "fqlite":
|
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
See sqlite3.{go,jq} for TODO Related to #27
out of scope?
The text was updated successfully, but these errors were encountered: