Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to optimize Local Database #62

Open
vkryl opened this issue Feb 9, 2018 · 5 comments
Open

Ability to optimize Local Database #62

vkryl opened this issue Feb 9, 2018 · 5 comments

Comments

@vkryl
Copy link
Contributor

vkryl commented Feb 9, 2018

Local Database size grows over time. It grows very fast when you receive messages with Instant View (or subscribed to some channels). For now there's no option to optimize local database.

@brickoffthewall
Copy link

How can I become informations about the new Update from April 22 - 2019?

The designated Telegram Bot has not yet been updated with the explanation of this update.

@shah-sudeep
Copy link

Does this feature still not implemented in tdlib?
Telegram X still says so, and that the data of secret chat will to be erased while doing so.

@RememberTheAir
Copy link

@shah-sudeep the issue being still open means tdlib doesn't support db optimization yet

@lam19892089
Copy link

Kích thước Cơ sở dữ liệu cục bộ tăng lên theo thời gian. Nó phát triển rất nhanh khi bạn nhận được tin nhắn với Chế độ xem tức thì (hoặc đăng ký một số kênh). Hiện tại, không có tùy chọn nào để tối ưu hóa cơ sở dữ liệu cục bộ.

#620

@jpage4500
Copy link

This is an old issue but I'm using TDLib and I noticed the DB size has grown to over 9 GIG on my device!

        authStateRequest.useMessageDatabase = true;
        authStateRequest.enableStorageOptimizer = true;

The Telegram app has a "Clear Local Database" option -- could at least something like this be added? Or a way to delete messages > a given timestamp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants