Many users are excited about Notion adding capabilities for databases over 100K rows because it should fix query latency and unlock uses like ledgers or market data, while some recall past frustrations splitting oversized tables.
Based on 6 visible X reactions from 12 accounts; directional sample.
Ask a question below.
Published answers will appear here.
i never tried it so far.. just assumed it wouldn't work:) but yeah.. markets sure.. tick level ohlcv blows past 100k trivially.. but more than the row count, the challenge would be to accomodate different write patterns... high frequency append only streams vs mutating entity tables.. anyways, excited to see how you guys handle pagination pains etc.. cool stuff..
@ivanhzhao @zachtratar @NotionHQ @connors I had to split over a million rows across 12-14 databases recently. 😭 It caused some major errors with workers I was running. I’m currently exploring BigQuery as a solution and Notion as the UI/collaboration/context.
@ivanhzhao @_clem @NotionHQ @connors Omg hope smth happens with those limits 🤞
@ivanhzhao @NotionHQ @connors This will be game changing.
Many users are excited about Notion adding capabilities for databases over 100K rows because it should fix query latency and unlock uses like ledgers or market data, while some recall past frustrations splitting oversized tables.
Based on 6 visible X reactions from 12 accounts; directional sample.
Ask a question below.
Published answers will appear here.