issues

5 rows where repo = 213286752 sorted by updated_at descending

View and edit SQL

Suggested facets: user, comments, author_association, created_at (date), updated_at (date), closed_at (date)

state

type

repo

  • pocket-to-sqlite · 5
id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association pull_request body repo type active_lock_reason
629473827 MDU6SXNzdWU2Mjk0NzM4Mjc= 5 Suggesion: Add output example to readme harryvederci 26745575 open 0     0 2020-06-02T19:56:49Z 2020-06-02T19:56:49Z   NONE  

First off, thanks for open sourcing this application! This is a suggestion to increase the amount of people that would make use of it: an example in the readme file would help.

Currently, users have to clone the app, install it, authorize through pocket, run a command, an then find out if this application does what they hope it does.

Another possibility is to add a file example-output.db, containing one (mock) Pocket article.

Keep up the good work!

pocket-to-sqlite 213286752 issue  
503234169 MDU6SXNzdWU1MDMyMzQxNjk= 2 Track and use the 'since' value simonw 9599 closed 0     3 2019-10-07T05:02:59Z 2020-03-27T22:22:30Z 2020-03-27T22:22:30Z MEMBER  

Pocket says:

Whenever possible, you should use the since parameter, or count and and offset parameters when retrieving a user's list. After retrieving the list, you should store the current time (which is provided along with the list response) and pass that in the next request for the list. This way the server only needs to return a small set (changes since that time) instead of the user's entire list every time.

At the bottom of https://getpocket.com/developer/docs/v3/retrieve

pocket-to-sqlite 213286752 issue  
503233021 MDU6SXNzdWU1MDMyMzMwMjE= 1 Use better pagination (and implement progress bar) simonw 9599 closed 0     4 2019-10-07T04:58:11Z 2020-03-27T22:13:57Z 2020-03-27T22:13:57Z MEMBER  

Right now we attempt to load everything at once - which caps out at 5,000 items and is really slow.

We can do better by implementing pagination using count and offset.

pocket-to-sqlite 213286752 issue  
589402939 MDU6SXNzdWU1ODk0MDI5Mzk= 4 Store authentication information as "pocket_access_token" etc simonw 9599 closed 0     0 2020-03-27T20:43:22Z 2020-03-27T20:43:59Z 2020-03-27T20:43:59Z MEMBER  

The pocket_ prefix will mean that the same auth.json file can be used for other Dogsheep tools without Pocket over-riding a value set by some other tool.

pocket-to-sqlite 213286752 issue  
503243784 MDU6SXNzdWU1MDMyNDM3ODQ= 3 Extract images into separate tables simonw 9599 open 0     0 2019-10-07T05:43:01Z 2019-10-07T05:43:01Z   MEMBER  

As already done with authors. Slightly harder because images do not have a universally unique ID. Also need to figure out what to do about there being columns for both image and images.

pocket-to-sqlite 213286752 issue  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);
Powered by Datasette · Query took 48.848ms · About: github-to-sqlite