by leeuw01 on 12/23/20, 12:51 PM with 38 comments
by misterdata on 12/24/20, 8:09 AM
Our users (researchers) had no problems learning the concepts of querying but didn't want to be bothered learning SQL syntax - hence we built this (also, our system does quite a bit of magic behind the scenes to allow mixing e.g. CSV data with data from a database, and also allows for things not easily done in SQL, e.g. pivot tables, so it's not just SQL).
by Cieplak on 12/24/20, 8:47 AM
A term made up by Fred Lakin describing a comment Peter Deutsch made at a VL talk by Scott Kim and Warren Robinett about a visual machine language they had invented.
Deutsch said something like:
> "Well, this is all fine and well, but the problem with visual programming languages is that you can't have more than 50 visual primitives on the screen at the same time. How are you going to write an operating system?"
This points out the obvious density advantage of text. This barrier has become known as the "Deutsch Limit," stated as:
> The problem with visual programming is that you can't have more than 50 visual primitives on the screen at the same time.
...
This is clearly a problem with visual representations. However, it is not immediately clear to me that a similar limit does not also exist in textual languages.
When textually programming I frequently use an Emacs window with about 50 lines of text on my 19" monitor. Anyone older than about 35 complains that they cannot read the text because the font is too small. I use a lot of whitespace in my programs, so we might assume that the 50 lines in the editor contain 40 meaningful lines. Most common programming styles dictate limiting the number of "primitives" or statements to one or two per line, giving my textual screen at most 80 primitives.
by sfgweilr4f on 12/24/20, 3:44 AM
SELECT * from customers
so... I'm kind of bummed out. The blocks seemed to not stick together. They'd just "island" and sit by themselves. I finally managed to push them together for a "SELECT FROM customers" combination of blocks. But there was a "clause" thing stuck on the screen.
I felt like this should be a really quick thing to do.
After all that I then got:
Ungültige Abfrage: Unknown table 'web1312.customers'
so the table I selected didn't even exist. Possibly.
Sadness.
(Maybe its a firefox thing? Can I blame firefox?)
by tangus on 12/24/20, 2:15 PM
I actually don't see how this is better than a cheat sheet with SQL keywords and autocompletion of tables/fields.
by xaedes on 12/24/20, 2:46 AM
by leeuw01 on 12/23/20, 12:51 PM
by ben509 on 12/24/20, 7:19 AM
by victor106 on 12/24/20, 2:44 AM
Anyone know of a tool that can parse a complex sql and generate a table diagram showing the various joins etc.,?
by 51Cards on 12/24/20, 3:44 AM
by renke1 on 12/24/20, 12:23 PM
by quantumwoke on 12/24/20, 9:09 AM
by hardwaresofton on 12/24/20, 6:39 AM
by ris on 12/24/20, 6:28 PM