Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Loading 500K Rows from SQLite Database Using SwiftData.

azamsharp's profile picture

Mohammad Azam

20,865 subscribers

34,262 görüntüleme • 3 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Using Expo with real-time synced SQLite means that instead of having to: • manage network requests • handle loading states • implement retry logic • orchestrate state management between your local cache and remote data You just write queries™
0:24

Using Expo with real-time synced SQLite means that instead of having to: • manage network requests • handle loading states • implement retry logic • orchestrate state management between your local cache and remote data You just write queries™

PowerSync

51,214 görüntüleme • 11 ay önce

Part 1 of 12: building a tiny SQLite-style database in C from scratch. Today is the REPL skeleton: the db > command line, getline, .exit, EOF handling, and the loop every future parser, row store, pager, and B-tree feature plugs into. This tiny command shell becomes a database.
3:30

Part 1 of 12: building a tiny SQLite-style database in C from scratch. Today is the REPL skeleton: the db > command line, getline, .exit, EOF handling, and the loop every future parser, row store, pager, and B-tree feature plugs into. This tiny command shell becomes a database.

tetsuo

16,367 görüntüleme • 3 ay önce

Delete blank rows using Excel shortcut keys
0:20

Delete blank rows using Excel shortcut keys

Computer Knowledge

13,219 görüntüleme • 4 ay önce

Stop Using Your Biceps on Cable Rows!
0:43

Stop Using Your Biceps on Cable Rows!

Muscle Freak

614,218 görüntüleme • 3 ay önce

Meet Database Agents. A team of li’l librarians in your database — keeping it up to date automatically using context from the page, your workspace, and the web. No more “we’ll update the database later.” Starting to roll out on Biz + Enterprise.
0:34

Meet Database Agents. A team of li’l librarians in your database — keeping it up to date automatically using context from the page, your workspace, and the web. No more “we’ll update the database later.” Starting to roll out on Biz + Enterprise.

Notion

299,577 görüntüleme • 5 ay önce

Kevin Maguire says its clear Reform are using the murder of Anne Widdecombe as a diversion from rows over 'gifts' and donations.
2:17

Kevin Maguire says its clear Reform are using the murder of Anne Widdecombe as a diversion from rows over 'gifts' and donations.

Saul Staniforth

834,322 görüntüleme • 1 ay önce

Here is my Vegas DefCon presentation from last week on how to hack the Dominion Voting machines. There is a unprotected SQLite database on the ICX voting machines that can be altered. It also stores the encryption keys in plain text.
3:52

Here is my Vegas DefCon presentation from last week on how to hack the Dominion Voting machines. There is a unprotected SQLite database on the ICX voting machines that can be altered. It also stores the encryption keys in plain text.

Mad Liberals

323,587 görüntüleme • 1 yıl önce

Opus 4.5 using frontend skill (Claude Pro) landing page + fullstack nextjs with sqlite db one-shot 🔥🔥🔥
0:29

Opus 4.5 using frontend skill (Claude Pro) landing page + fullstack nextjs with sqlite db one-shot 🔥🔥🔥

Melvin Vivas

72,140 görüntüleme • 9 ay önce

Database table size impacts performance in more ways than one: a) B-tree depth. Using 8k pages and a 16b uuid: 1 level = ~370 rows 2 levels = ~138k rows 3 levels = ~50m rows 4 levels = ~20b rows The lookup cost on a table with 100k rows is not the same as one with 1b rows. This can apply both to the table itself (MySQL cluster index) as well as the indexes. Sometimes a single query requires many of them. b) Small table → fits in RAM → fast reads. The larger the table, the more likely to read from disk plus churn the cache. c) # of indexes. Each adds maintenance overhead for insertions, and for Postgres vacuum overhead as well. Keep an eye on this! It's useful to take regular stock of your tables + indexes. Clean bloat. Remove unused indexes. Partition if needed.
0:58

Database table size impacts performance in more ways than one: a) B-tree depth. Using 8k pages and a 16b uuid: 1 level = ~370 rows 2 levels = ~138k rows 3 levels = ~50m rows 4 levels = ~20b rows The lookup cost on a table with 100k rows is not the same as one with 1b rows. This can apply both to the table itself (MySQL cluster index) as well as the indexes. Sometimes a single query requires many of them. b) Small table → fits in RAM → fast reads. The larger the table, the more likely to read from disk plus churn the cache. c) # of indexes. Each adds maintenance overhead for insertions, and for Postgres vacuum overhead as well. Keep an eye on this! It's useful to take regular stock of your tables + indexes. Clean bloat. Remove unused indexes. Partition if needed.

Ben Dicken

212,291 görüntüleme • 4 ay önce

So you can just give it a postgres URL (or sqlite db file) and it will just... explore it and offer to build things. Even with a crazy nonstandard (from Ecto perspective) database. The search bar crashed, I sent the logs to the agent, and boom realtime searching
1:27

So you can just give it a postgres URL (or sqlite db file) and it will just... explore it and offer to build things. Even with a crazy nonstandard (from Ecto perspective) database. The search bar crashed, I sent the logs to the agent, and boom realtime searching

Chris McCord

12,762 görüntüleme • 1 yıl önce

I promised a longer video on how to build a full-stack ICP app, powered by SQLite. Here it is! This is a nose to tail walkthrough, we look at database migrations, automatic input validation, DTO objects, performant frontend queries using Tanstack Query and lots more. Links to demo app, libraries and YT video in the responses. 🌱
33:58

I promised a longer video on how to build a full-stack ICP app, powered by SQLite. Here it is! This is a nose to tail walkthrough, we look at database migrations, automatic input validation, DTO objects, performant frontend queries using Tanstack Query and lots more. Links to demo app, libraries and YT video in the responses. 🌱

Kristofer

13,063 görüntüleme • 11 ay önce

Kyushu University released more than 1500 3D models of animals and plants using a photogrammetry technique, taking digital photos from multiple angles [database: [full paper:
1:00

Kyushu University released more than 1500 3D models of animals and plants using a photogrammetry technique, taking digital photos from multiple angles [database: [full paper:

Massimo

932,357 görüntüleme • 2 yıl önce

Building Vector Database from Scratch
0:57

Building Vector Database from Scratch

Mohit Mishra

23,126 görüntüleme • 1 yıl önce

Epicenter (epicenter) is building a database for your mind. They're designing a Svelte ecosystem of apps sharing a local memory: a folder and SQLite file. Open-source, open-format, and fully yours. Congrats on the launch, Braden Wong!
2:11

Epicenter (epicenter) is building a database for your mind. They're designing a Svelte ecosystem of apps sharing a local memory: a folder and SQLite file. Open-source, open-format, and fully yours. Congrats on the launch, Braden Wong!

Y Combinator

17,815 görüntüleme • 1 yıl önce

So you forgot how you fixed that bug the other day. 😬 No worries. GitHub Copilot CLI remembers. With its local SQLite database of your session history (and a full-text search index), you can instantly pull up context from your previous work. ✅ Install Copilot CLI and save brain space. ⬇️
1:10

So you forgot how you fixed that bug the other day. 😬 No worries. GitHub Copilot CLI remembers. With its local SQLite database of your session history (and a full-text search index), you can instantly pull up context from your previous work. ✅ Install Copilot CLI and save brain space. ⬇️

GitHub

47,229 görüntüleme • 6 ay önce

The 1.4 release of DuckDB supports using a DuckDB database to serve vector tiles! Of course, I had to try this out in R. Check it out: all 242,000 US Census block groups dynamically served as vector tiles from a DuckDB database, displayed on a MapLibre map from R in Positron.
0:31

The 1.4 release of DuckDB supports using a DuckDB database to serve vector tiles! Of course, I had to try this out in R. Check it out: all 242,000 US Census block groups dynamically served as vector tiles from a DuckDB database, displayed on a MapLibre map from R in Positron.

Kyle Walker

45,518 görüntüleme • 10 ay önce