Persistence module (database interaction) #6
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#5 RSS update manager
Miroslavsckaya/tg_rss_bot
#7 Telegram Command Processor
Miroslavsckaya/tg_rss_bot
#10 Telegram module
Miroslavsckaya/tg_rss_bot
#15 Migrate persistence module to PostgreSQL
Miroslavsckaya/tg_rss_bot
#16 Database initialization and migration
Miroslavsckaya/tg_rss_bot
#18 Refactor/Optimize transactions
Miroslavsckaya/tg_rss_bot
Reference: Miroslavsckaya/tg_rss_bot#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To implement a module which interacts with the database to:
COUNT()
on the linking table?delete
last +insert
new)Recommendations:
@Miroslavsckaya, let's use SQLite in MVP to save time.
I'll create another ticket for PostgreSQL migration.
ok
@Miroslavsckaya we also need to have migrations to be able to properly develop the project as a team. So I've created #16 for you. You can implement that after imlementing a draft of this task.
We forgot about
get_user()
method. So we should implement it too 🤷♂️