4 ms·

If you have more than a few thousand records, this is the wrong tool for the job. I've used Google Sheets as a "database" for a few applications in the past. In

by hliyan 2y ago

If you have more than a few thousand records, this is the wrong tool for the job. I've used Google Sheets as a "database" for a few applications in the past. In each case, it was an internal tool that did not generate more than a few thousand records, if that.

p2detar 2y ago
A few thousand like the product of rows*cols? Just curious.
- baobun 2y ago
  records = rows
layer8 2y ago
Even text files (like CSV) are fine for the amount of data the OP has trouble with, and Excel certainly is, so it’s unclear why Google Sheets should already balk on that. Google Sheets has a limit of 10 million cells per sheet (so for 25000 rows that would be 400 columns), and really shouldn’t be running into errors for sheets below that limit.
diggan 2y ago
> If you have more than a few thousand records, this is the wrong tool for the job. Just to be precise, Google Sheets might be the wrong tool for the job. Other spreadsheet applications can handle "more than a few thousand records" easily, seems this is a Google Sheets specific issue.
- mattigames 2y ago
  I wouldn't be surprised if it's not fixed on purpose, they do have cloud DB offering and all that overpriced jazz to sell you.
baobun 2y ago
Can also be a feature to cap the potential scale for a PoC you want to keep from getting productized as-is.
zie 2y ago
I guess? 25k rows with 10 columns shouldn't be a big deal. LibreOffice, Excel, Numbers, they all handled this data without trouble. It is 99% static data, it would be updated maybe once a year if that. The point was to give users something they were familiar with to look at the data, search it, etc. While being in the "cloud" so I only had to update one place whenever I do get tasked with an update and to handle authn/z easily with no hassles. Anyways, I used SQLite and a very simple web frontend(it had 3 screens: search, table view and record view). Solved the problem and moved on. Search just filtered the table view.

by hliyan 2y ago

p2detar 2y ago

A few thousand like the product of rows*cols? Just curious.

baobun 2y ago
records = rows

layer8 2y ago

Even text files (like CSV) are fine for the amount of data the OP has trouble with, and Excel certainly is, so it’s unclear why Google Sheets should already balk on that. Google Sheets has a limit of 10 million cells per sheet (so for 25000 rows that would be 400 columns), and really shouldn’t be running into errors for sheets below that limit.

diggan 2y ago

> If you have more than a few thousand records, this is the wrong tool for the job. Just to be precise, Google Sheets might be the wrong tool for the job. Other spreadsheet applications can handle "more than a few thousand records" easily, seems this is a Google Sheets specific issue.

mattigames 2y ago
I wouldn't be surprised if it's not fixed on purpose, they do have cloud DB offering and all that overpriced jazz to sell you.

baobun 2y ago

Can also be a feature to cap the potential scale for a PoC you want to keep from getting productized as-is.

zie 2y ago

I guess? 25k rows with 10 columns shouldn't be a big deal. LibreOffice, Excel, Numbers, they all handled this data without trouble. It is 99% static data, it would be updated maybe once a year if that. The point was to give users something they were familiar with to look at the data, search it, etc. While being in the "cloud" so I only had to update one place whenever I do get tasked with an update and to handle authn/z easily with no hassles. Anyways, I used SQLite and a very simple web frontend(it had 3 screens: search, table view and record view). Solved the problem and moved on. Search just filtered the table view.