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
Running this script can take several hours against a large notes database.
Would be neat if it could run against just the notes that have been modified since it last ran. Could pull the max updated date and then keep on looping until it finds one modified before then.
Problem is I don't actually know what order it iterates over the notes in.
The text was updated successfully, but these errors were encountered:
It looks like the iteration order is most-recently-modified-first - I tried editing a note a bit further back in my notes app and it was the first one output by apple-notes-to-sqlite --dump.
In terms of the UI: I'm tempted to say that the default behaviour is for it to run until it sees a note that it already knows about AND that has matching update/created dates, and then stop.
You can do a full import again ignoring that logic with apple-notes-to-sqlite notes.db --full.
Running this script can take several hours against a large notes database.
Would be neat if it could run against just the notes that have been modified since it last ran. Could pull the max
updated
date and then keep on looping until it finds one modified before then.Problem is I don't actually know what order it iterates over the notes in.
The text was updated successfully, but these errors were encountered: