-
Couldn't load subscription status.
- Fork 579
implement .dbtotxt and dbpage vtab #3834
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
base: main
Are you sure you want to change the base?
implement .dbtotxt and dbpage vtab #3834
Conversation
72a4fef to
6b1ee7c
Compare
6b1ee7c to
56df015
Compare
0284241 to
d110d1d
Compare
|
If used on empty db, we currently get this error but it is due to #3441 turso> .dbtotxt
| size 0 pagesize 4096 filename wed
/****** ERROR: Database is empty, header does not exist - page 1 should've been allocated before this ******/
turso> |
|
I m thinking maybe it would be nice if we could do smthng like
and we only display page 2 , sqlite dont have this, but i had this issue in large dbs i have to scroll forever or pipe it into a file and read from file |
turso> .dbtotxt --page 2
| size 8192 pagesize 4096 filename :memory:
| page 2 offset 4096
| 0: 0d 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 ................
| end :memory:
turso> |
|
Maybe i am getting ahead of myself but why cant we just use a seperate screen for this? for eg: similar to how if anyone think this is a good idea, please let me know and i will do that. for now i am not doing it as i am not really sure if its good or bad thing. |
closes #3833
sqlite dont support this but i think this is nice to have a --page flag
Note:
sqlite allows to write into
sqlite_db_page, we do not yet, - issue #3836 - i'm not really sure why this is needed, so i didn't bothered with it.