franciscop

drive-db

JavaScript2015–2023

franciscop / drive-db · Archived

drive-db

:bar_chart: Use Google Drive spreadsheets as a simple database

Data & Databases Productivity

Explore on GitHub Read Hacker News discussions

3Distinct people

18Mentions

0Explicit recommenders

821GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

:bar_chart: Use Google Drive spreadsheets as a simple database

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:27:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2015-01-19 22:23:11 UTC to 2023-02-27 01:24:15 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	3	1	2
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	3	2	1
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	7	1	6
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	2	0	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1

What Hacker News says

7 sources

j_s·Nov 3, 2017

Google Spreadsheets and Python | https://news.ycombinator.com/item?id=13668916 (2017Feb:140comments) ・SQL into Sheets - http://pastebin.com/ACwqc5um ・LibreOffice Calc server - https://github.com/robsco-git/spreadsheet_server ・Sheets API (JS) - http://chriszarate.github.io/sheetrock/ | https://github.com/theoephraim/node-google-spreadsheet ・Grunt / Jekyll - https://github.com/stpe/grunt-gss-to-json ・simple read-only (JS) - https://github.com/franciscop/drive-db | https://github.com/digplan/gsheet-web ・auth proxy (Golang) - https://github.com/VLO-GDA/server-app

In Connecting to Google Sheets with Python

franciscop·Nov 3, 2017

I made the same thing for Node.js but without credentials. The main gotcha is that your spreadsheet is public (but unlisted). It also has some basic commands to use it as a Mongo database, or just use the array of data: https://github.com/franciscop/drive-db/ I also made a small tutorial of how to use it: https://serverjs.io/tutorials/spreadsheet/

In Connecting to Google Sheets with Python

franciscop·Jul 31, 2017

It seems everyone is recommending books/courses/similar. I'll go the other way around. This is difficult for me to say, but I think I am an expert in CSS+JS. I know the inner workings and really advanced things of CSS, and while JS API is quite broader I know some in-depth JS APIs that your average developer doesn't even know exists. I got to this point first in CSS and then with JS by making side projects and focus each one on a different advanced concept. I will also say it in 1st person as I experienced it as it might sound insulting otherwise: - Don't get attached to my code. My code is crap. My 6+ months old code is a lot more crap. Always think ways of improving it. Sidenote: try to make it as standard of possible. Initially I did things my way until my open source started to get some traction and it was a mess. - Once I got past th

Read the rest

e basics and mid-level, what I did to keep up learning was to try to focus each small side project around a technology I wanted to learn in-depth. Examples: Umbrella JS[1] is about a modular codebase, Superdom [2] is about Proxy, drive-db [3] is about talking with external APIs and DB design, etc. - Push the limits on the technology on each project. Don't just do the basics and call it a day, try to find what is possible and what is not. Examples: Umbrella JS'[1] performance is similar to jQuery thanks to using the prototype properly, Superdom's [2] Proxies are recursive-ly, drive-db [3] is cached for maximum performance, etc. - If I don't use it no one will. Publish it for feedback after it is polished from feedback from different projects. Focus on the positive comments to keep going and on the negative ones to keep improving. Because I know my code is crap, when someone says X is quite bad I agree on principle and find a way to fix it or prove to myself that it _was_ the right approach. Examples: Umbrella JS initial code wasn't good for the different ways of importing it, so I added a UMD-ish kind of thing. Superdom was really buggy so I had to write a few tests all around it. drive-db was not good for promises-based code so I converted it to ES7. There is something I haven't made which I am trying now that it's reading and understanding large, public projects such as Ghost. I have done something similar while contracting, but those closed-source project's code is IMHO generally messier and you are normally trying to go for business requirements, not really focusing on pleasure/learning so much. [1] https://umbrellajs.com/ [2] https://superdom.site/ [3] https://github.com/franciscop/drive-db

In Ask HN: Resources for learning advanced JavaScript and React

franciscop·Apr 6, 2017

As a dev of an unrelated lib who cares about making good documentation this is a really valuable comment; I'm guilty of doing this partially for example in https://github.com/franciscop/drive-db where I link to MongoDB platform for the more advanced selectors. In my experience good documentation takes around 3x-5x of the time of writing the code (excluding tests and tutorials), so while I hate seeing libraries without a decent documentation I totally understand it. Edit: also it is in alpha, where writing documentation many times backfires you and you have to remove large pieces of it wasting your time.

In Planck.js – JavaScript rewrite of Box2D physics library

franciscop·Mar 28, 2017

I created something simpler but based on Google Docs and just retrofitted promises into it: https://github.com/franciscop/drive-db

In Show HN: SpreadsheetDB – A database that you can query with spreadsheets

franciscop·Feb 17, 2017Submission

Ask HN: Why some stories rise while others go unnoticed?

I just saw this story "Google Spreadsheets and Python." in the #1 of HN. I made a library that does almost the same for Node.js ( https://github.com/franciscop/drive-db ) but it didn't get so much attention compared to it [1]. So my question is, what influences on the ranking/votes of the stories? I'm not complaining, just curious, this is my best guess: - Tech: innovative, quality, etc - Landing page/PR (or "hacker PR") - Company name behind it - People you know in the industry+silicon valley? - What else? I have some ideas as I've landed few projects on the front-page of HN, but somehow it seems quite random. I have observed a direct relationship with the mentioned points and appraisal/hate in the comments, but not with the vote count. So does anyone have anything to add? [1] https://news.ycombinator.com/item?id=8914508

5 points · Open discussion

franciscop·Feb 17, 2017

You might like a small library I made then, it's really similar to Twillio one but in Node.js but a lot easier to set-up (read-only): - https://github.com/franciscop/drive-db

In Google Spreadsheets and Python