Allow Additional Databases for Data Security and Performance
Dear Sir,
A feature to enable switching between multiple databases within our current application. This would allow us to create separate database files for each year, enhancing data security and preventing performance degradation due to large database sizes.
By implementing a button or selection box within the application, users could easily switch between different database files, ensuring seamless access to relevant data.
This approach would provide the following benefits:
-Enhanced Security: Isolating data into separate files reduces the potential risk of unauthorized access or data breaches. -Improved Performance: Smaller, more focused databases can lead to faster query execution and overall system performance. -Simplified Data Management: Organizing data by year facilitates efficient data management and analysis.
We believe that this feature would significantly improve the overall efficiency and security of our application.
Please let us know your thoughts on this proposal.
Muhammad
I can add this capability in a future release, but it will be a while before I can work on it.
@rffrasca Thank you so much for your reply. We will wait for that sir.
Regards.
Hello @Sohail2949000 - Since you're now using MySQL, is this still a concern?
Sir
Yes thanks to you ☺️ we now connected to MySQL.
If adding all files in single database will not effect performance of pdfkeeper than it is solved.
Does PDFkeeper comes with a limit of files or total size or mysql?
Do you feel that there is a need to create multiple databases? If so, then PDFKeeper will need an enhancement.
To answer your question, PDFKeeper does not impose any limits. However, you may run into limitations based on your environment.
I think it is needed at least we can use that on sqlite version where we already stored documents for a whole 2 years and database size is increased alot.
Now we switched to mysql starting from 2025.
What I meant was "Do you feel that there is a need to create multiple databases in the MySQL environment?"
@rffrasca I think yes it would be supportive in long term to have option to separate database based on years