kengruven
commented
6 years ago It looks like there's a lot of space after "History1.db" in your screenshot. Did some spaces get accidentally added to the path?
Open Chris-Knight opened 6 years ago
kengruven
commented
6 years ago It looks like there's a lot of space after "History1.db" in your screenshot. Did some spaces get accidentally added to the path?
Chris-Knight
commented
6 years ago Well it turns out not just spaces but several hidden lines of paths and partial paths and files that were are on a completely separate document that I was trying to figure out how to combine plists before I read on the github site that you can't. Anyway, I deleted everything except the path to the sqllite file and there were no spaces before or after and pressed enter and nothing happened and then scrolling to find that it added all the extraneous path stuff back in. I can't tell if it is the same as it was before or not because I can't see everything with the way the cursor rectangle only shows part of a single line and not everything all at once. I tried to delete it again and it all appeared to be deleted, except the correct path. And it added it all back in again. So, I deleted it all again and pressed enter and it worked. Where all the paths came from I've no idea. Why they would not delete I have no idea. I am glad it seems to be working now, It is late here and I will compare it to what Base.app is showing in the morning.
Thank you for your reply. I really do appreciate it.
Best regards, ~Chris
Ken Harris mailto:notifications@github.com January 20, 2018 at 10:43 PM
It looks like there's a lot of space after "History1.db" in your screenshot. Did some spaces get accidentally added to the path?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kengruven/strukt-bugs/issues/28#issuecomment-359227838, or mute the thread https://github.com/notifications/unsubscribe-auth/ACfAujydMxlaJfRh5FX3lIp3w3xGAnAGks5tMtydgaJpZM4Rlqon.
-- Sent from Postbox https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
kengruven
commented
5 years ago FWIW, the error messages were improved a bit. It reports (as of 1.5.4, a year ago) different errors for "This file does not exist", "Not a SQLite file", and "Error opening this SQLite file".
That's not a complete solution to every aspect of this issue, but it should make it a tiny bit easier to track down.
kengruven
commented
4 years ago You ran into several usability issues here, and I'm going to leave this ticket open until I've made progress on all of them.
For my own convenience, I'll summarize here the issues I see with Strukt-as-SQLite-tool. In addition to the improvements already made to error messages, I see:
Feel free to add any items to this list that you think I missed.
I would like to see the documentation and samples expanded to give more information with "how" to work with the supported database formats. The application, on paper, sounds like a great tool, in practice however, I have found it to be terribly unintuitive and non-mouse friendly. I am trying to do something very simple, open a Safari browser history file. The recent versions of Safari save the browser history in History.db located in ~/Library/Safari. It is a sqlite file. I can open it easily in Base.app (great app on the App Store) and in DBAppX.app which I also found on the App Store and like the UI a lot. I know the file is good and is a sqlite file. Strukt, after much effort to figure out how to, finally got rid of the message it needed access buy finally granting access to the entire volume since granting access to the file just gave a message it needed access to the folder also. Anyway, now Strukt tells me it isn't a sqlite file.
I am either still not doing something right and/or Strukt has a problem with a sqlite file that two SQLite reading/editing apps do not. This is Base.app looking at it,
This is DBAppX.app looking at the same table in the same database (different records though).
This app wasn't exactly cheap - the advert on the App Store said it had a manual and that helped persuade my purchase. The manual is a good start but is lacking in depth and breadth. I would sure like to be able to figure out how to use the app to work with History.db.