Increase History Size to 99 999 #1144
Labels
feature
New feature request
Comments
|
Depending on what you store in the app, even 10k items can be too much data. Opening such tab slows down that application too much (CopyQ uses simple data format to store tabs). I won't increase the limit unless the data format changes. It's better to use tabs to mange huge number of items. There are couple of commands that simplify this. If you really need this and since you're a programmer, you can try changing the limit in code and recompile the app. But if you use other formats than plain text you might see performance regressions. |
|
First of all, for the excellent work done with CopyQ, this program is by far one of the best that exists in this activity. I am programmer in Delphi "Pascal" I do not know how to program in C ++ Another way of solving is when you reach Historical Limit create a Backup or Automatic Guide with Archiving Month and Year. |
|
@luapfr , I bumped into this issue as well. Check out this backup script I wrote which backs up plain text clips to a local searchable sqlite database |
|
maybe you can Add a function that can switch the history database |
Closed
hluk
added a commit
that referenced
this issue
Nov 15, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 15, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 15, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 16, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 18, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 18, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 18, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 18, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 18, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 21, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 21, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 21, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 21, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 22, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 4096. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 26, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 1024. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Nov 26, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 1024. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Dec 10, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 1024. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
hluk
added a commit
that referenced
this issue
Dec 13, 2023
Saves larger data in separate files. Data from these files are loaded into memory only when needed. The threshold value in bytes is stored as "item_data_threshold" hidden option. Item data that are larger than this value will be stored in separate files. The default value is 1024. Setting value to 0 would store all non-empty item data to separate files. A negative value disables the functionality and saves all into tab data file as before. Cleans up data directories on idle and exit. Files in synchronized directories now also work the same. This change is not backwards-compatible. Going back to previous release could mean losing some data. But going to a new release again would parse the data correctly. Workaround is to set "item_data_threshold" to a negative value and trigger storing data tab (e.g. moving an item back and forth). Fixes #1144
|
Fixed in #2541. This will be available in the next release with performance improvements related to tab/item data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the Historico has a limit of 9 999 would be very interesting an addition, as I am a programmer I use a lot of Transfer, and the Limit of 9 999 is easily reached.
With 99 999 it would be perfect.
Thankful.
The text was updated successfully, but these errors were encountered: