Franchise – An Open-Source SQL Notebook • Hacker News Board

Re: Franchise – An Open-Source SQL Notebook

#61

Post by awake » Fri, Sep 22, 2017, 5:03 PM UTC

I think this is a really clean product but I have a couple of questions.

1. I'm dealing with a dataset with >10M rows. Is there any way to kill a query that is currently running? I noticed at least with postgres that a long running query would stop me from performing any other queries.

2. The hashtag notation is very nice but would it be possible to cache the results of the hashtag without having to run the same query over again. This would more closely resemble the behavior of jupyter notebook, where results in previous cells can be recalculated by running those cells, but can be quickly accessed without recalculation.

Re: Franchise – An Open-Source SQL Notebook

#62

Post by j_s » Sun, Sep 24, 2017, 2:30 AM UTC

geokon wrote: post #12

This looks really cool! I've been meaning to learn SQL for a long time, but I'm unfortunately in an unrelated field. Could anyone recommend some resources for learning SQL? Preferable targeted towards an experienced programmer

Further discussion(s): https://hn.algolia.com/?query=learn%20sql

Re: Franchise – An Open-Source SQL Notebook

#63

Post by statsig » Sun, Sep 24, 2017, 6:59 PM UTC

This looks incredible! Congrats, guys! Does it support Google Authentication for sign in and data access restriction features for sensitive data?

Re: Franchise – An Open-Source SQL Notebook

#64

Post by lakkal » Tue, Sep 26, 2017, 3:39 PM UTC

bijection wrote: post #6

Co-creator here! We wanted * A simple, flexible SQL client * A notebook interface that lets you drag stuff around and view things side-by-side * Query CSVs, JSON, and XLSX documents fully in-browser with Emscripten + SQLite * Postgres, MySQL and BigQuery through a local connection bridge. Your data never touches a third party server. I’ll be here with @antimatter15 for the rest of the morning answering questions!

This looks great! Is there any chance that it will work with MS SQL Server? Sadly (i.e. over my recommendations) my company uses it rather than PostgreSQL.