mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

348K
active users

#sqlite

12 posts11 participants0 posts today

Дистанционное управление шлагбаумом с помощью MTC Exolve и GSM модуля

Несмотря на то, что я системный аналитик, проклятие, которое начинается с фразы «тыж программист…», иногда преследует и меня. Недавно у меня спросили совета, как сделать так, чтобы для нужных людей шлагбаум удаленно открывался без транспондера и сложных систем. К сожалению, сходу я не придумал ответа на вопрос, но задачка показалась мне любопытной, и я немного изучил вопрос. Решение нашёл быстро — в качестве аппаратной части можно использовать GSM-реле, а контроль доступа реализовать с помощью микро сервиса для переадресации вызова. И поскольку у меня наличествовал тестовый доступ к

habr.com/ru/companies/exolve/a

ХабрДистанционное управление шлагбаумом с помощью MTC Exolve и GSM модуляНесмотря на то, что я системный аналитик, проклятие, которое начинается с фразы  «тыж программист…», иногда преследует и меня. Недавно у меня спросили совета, как сделать так, чтобы для нужных...
Continued thread

I updated a bunch of stuff in the project, especially split the single database that was getting way too big for SQLite + microSD to handle gracefully (more than 30s) and I updated the README with new screenshots

I’m now storing my sensor readings in two database files:

  • the big one that I’ve been using from the start, but not using any more
  • a new one that gets created each day, and that’s the one that the graphs are now using

This way, the daily databases are kept small, which makes querying them fast (mostly for the pretty graphs), and I also still have a giant single database for offline statistics (should I need that)

I'm a database extremist. I default to #SQLite for pretty much anything.

As an independent software consultant, I need time tracking and CRM like anyone else. Guess what? It's just a single SQLite database file. :D Has worked wonderfully for years using just a database viewer app. (Tableplus, if you're wondering.)

But now, with this wonderful tool from Rune Kaagaard, I can hook up my database to Anthropic's Claude, and get insights into my time spent as well as my connections, just by chatting with Claude Sonnet 3.7.

Wild! :D

github.com/runekaagaard/mcp-al

A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL. - runekaagaard/mcp-alchemy
GitHubGitHub - runekaagaard/mcp-alchemy: A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL.A MCP (model context protocol) server that gives the LLM access to and knowledge about relational databases like SQLite, Postgresql, MySQL & MariaDB, Oracle, and MS-SQL. - runekaagaard/mcp-alchemy

Anyone using #litestream for an #sqlite DB

I have a 3GB database, and Litestream is replicating it to another server. However, it seems to be running out of control with disk space. On the original server (where the live DB is) is a
generations folder under the hidden litestream folder. It is full of WAL files. Currently over 37,000 files consuming 118GB of disk space.

My config includes
retention: 24h and retention-check-interval: 1h with a snapshot-interval: 4h. I understood it would delete anything older than 24 hours. Am I doing something wrong? These wal files go back to the day I started using litestream

#GoToSocial #gts @gotosocial@thefedi.forum

I tend to hop a bit, between #sqlite and #postgres. So much that the nuances of each keeps merging for me. 😅

Interestingly enough, sqlite is the one my brain defaults to. You simply dumb everything way down. 😄 Which can actually give some performance improvements on postgres.