SQLite może być świetny w dużej skali. Zdziwieni? Czy faktycznie system zarządzania bazami danych kojarzący się z malutkimi, prostymi aplikacjami ma szansę zaistnieć w większych przedsięwzięciach? Warto zapoznać się z tym tekstem.
#SQLite #skalowanie #ArchitekturaOprogramowania
https://rivet.gg/blog/2025-02-16-sqlite-on-the-server-is-misunderstood
Hey all, I wrote a #PHP #SQLite #OpenSource forum called #Threadbare - https://github.com/Moult/threadbare
If your community is mailing list scale (i.e. not huge multilingual multicategory nested threads) check it out. If you're looking for an alternative to works-only-with-JS needs-containerisation logs-everything and want something minimal with performance near to a static site, it might be for you. Would love feedback and testing and security advice!
See https://community-test.osarch.org/ for demo.
Finally came up with a project to learn #Rust with. Not moving particularly fast, but it's making me spend a lot of time considering the implementation of data structures with ownership and lifetimes in mind.
I've been away from system-level programming for a while and last time I did any it was #C++ which is its own kind of pain.
Working on building up structures backed by a #sqlite #database as well, so getting #SQL practice also.
沙丁魚罐頭:使用 Rails 實現 SQLite 多租戶架構
➤ 克服 ActiveRecord 的限制,實現高效能多租戶架構
✤ https://blog.julik.nl/2025/04/a-can-of-shardines
本文探討了在 Rails 應用程式中實作「每個租戶一個資料庫」架構的挑戰。作者分享了過去在維護一個使用此架構的應用程式時遇到的問題,並指出現有的多租戶 gem (如 Apartment) 也存在類似的線程安全問題。文章深入探討了 ActiveRecord 連線管理機制,以及 Rails 如何使看似簡單的任務變得複雜,並提供了一個可行的解決方案:一個中間件,能有效處理多租戶環境下的資料庫連線。作者強調了使用 SQLite 作為小型專案的優勢,例如易於配置、備份及除錯,並指出此架構能有效限制資料庫規模,降低複雜性。
+ 這篇文章深入淺出地分析了 Rails 多租戶架構的難點,對於正在考慮類似方案的開發者來說,非常有參考價值。
+ 作者的經驗分享很實用,提供的中間件解決方案讓我看到了希望,可以嘗試應用在我
#Rails #SQLite #多租戶 #資料庫架構
Thank you!
In #SQLite: LIKE is case-insensitive by default for ASCII characters (like normal English letters A–Z).
tinysparql (https://tracker.gnome.org/) as an rdf foundation to #localfirst ... i'd watch a whole talk on that. this feels like a fun way to get away from the pain shoehorning sync engines into sql dbs.
one thing i certainly love about side projects is that it gets us out of the daily perpetual work rabbit whole with endless pre-defined constraints!
for this homelab/ #iott sensor stuff i finally got to play with #sqlite and i’m really loving it. since everything is also running locally (and i finally made sqlite indexes work) this home sensor page for my e-ink display loads *SO FAST* with just a couple of ms
A relire : litecli, un client SQLite en ligne de commande
https://blog.shevarezo.fr/post/2020/09/22/litecli-client-sqlite-ligne-de-commande
If this message made it to you, it means the migration from #GoToSocial 0.18.3 to 0.19.0 went ok. The whole upgrade process, database migration stuff included, took only a couple of minutes; the #SQlite database is 1GB large. Of course, it runs on #NetBSD; using the official build.
v0.1.6 release - Wikimusic
https://codeberg.org/jjba23/wikimusic
stability improved, add ASCII size settings for web and become more EWW friendly (eased also thanks to SSR from #lisp )
visit my instance at : https://wikimusic.jointhefreeworld.org
@leogdion For #SQLite I also have Lighter, which I think is actually really good: https://github.com/Lighter-swift
And for Core Data I have replicated the #SwiftData macros: https://github.com/Data-swift/ManagedModels/
This by @mattiem might also be relevant to your article: https://mastodon.social/@mattiem/114359442297769327
@argv_minus_one
If it is actually written, yes. But #SQLite might detect there is no actual change and not declare the page dirty. And even if it is declared dirty, the row size will not change, so the B-Tree structure will be stable.
The page has to be read anyway, so both the disk cache and the SQLite page cache are primed. Except for hi-speed, hi-volume applications, I would not worry in advance. Premature optimization is the root of all evil.
@argv_minus_one
CREATE TABLE T1 (
id INTEGER PRIMARY KEY NOT NULL
, tx TEXT UNIQUE
);
INSERT INTO T1 (tx)
VALUES ('abc'),('def'),('ghi');
SELECT * FROM T1;
id tx
-- ---
1 abc
2 def
3 ghi
INSERT INTO T1 (tx) VALUES ('def') ON CONFLICT (tx) DO
UPDATE SET id = id + 0
RETURNING id;
id
--
2
I am disappointed to find that, with #SQLite, an INSERT statement with both ON CONFLICT DO NOTHING and RETURNING clauses won't return anything if there is a conflict.
I have a table that's basically just for interning frequently-used strings. It has a numeric ID column and a unique text column, and I want to get the ID for a given string, inserting if necessary.
With this RETURNING behavior, that has to be done in two steps, not one.
#Coding_Fridays is back : K-nn classifier in SQLite
Watch the full video in the Youtube channel central
>> https://youtu.be/gFe5S2G9GgI
This is a set of SQL queries demonstrating how in-server data processing can enable some basic data analytics.
Enable captions for more details and walk-through. Source code available at the Github repository (see channel info).
#Coding_Fridays is back : K-nn classifier in SQLite
Watch the full video in the Youtube channel central
>> https://www.youtube.com/@apneacoding
This is a set of SQL queries demonstrating how in-server data processing can enable some basic data analytics.
Enable captions for more details and walk-through. Source code available at the Github repository (see channel info).
#Coding_Fridays is back : K-nn classifier in SQLite
Watch the full video in the Youtube channel central
>> https://www.youtube.com/@apneacoding
This is a set of SQL queries demonstrating how in-server data processing can enable some basic data analytics.
Enable captions for more details and walk-through. Source code available at the Github repository (see channel info).
Oh joy, another Kafka-length ode to SQLite's virtual tables! Apparently, all you need for "true transactional integrity" is a few
magical
hooks. Because, obviously, row-level updates are for amateurs.
https://misfra.me/2025/sqlite-transactions-and-virtual-tables/ #SQLite #SQLiteVirtualTables #TransactionalIntegrity #ProgrammingHumor #SoftwareDevelopment #HackerNews #ngated