Ideas to improve the user and developer experiences of databases
1–10 of 56 posts
Re: Ideas to improve the user and developer experiences of databases
#2A couple things i'd love to have:
* native partitioning
* something like Materialized (where it's easy to specify data that is derived or denormalized).
Re: Ideas to improve the user and developer experiences of databases
#3Wow so cool
Re: Ideas to improve the user and developer experiences of databases
#4Lambdas would be nice, as the author says there are external options. Postgres has the notify function that lets you build this sort of thing.
https://gist.github.com/colophonemes/9701b906c5be572a40a84b0...
Re: Ideas to improve the user and developer experiences of databases
#5The main thrust seems to be tooling in the db to give developers some idea of the performance impact of the code they write.
But most programmers are using frameworks and ORMs and things that hide away what is actually happening with the database. A normal developer can look at a chunk of code on their side and have no real idea of what is happening on the database behind them.
What webdevelopers need is backend profiling information e.g. actual SQL queries and timings, shown beside all the frontend profiling information (e.g. in webdeveloper tools in the browser).
This profiling introspection can come from tooling in front of the database(s).
I recall seeing a blog about how the Stackoverflow team have nice tooling that does this for them. (Impossible to google for words like "stackoverflow profiling" and things!)
Re: Ideas to improve the user and developer experiences of databases
#6I’d like a tool that automatically suggests which indexes to add/remove, including use of different types of indexes and partial indexes, based on the queries being performed. Even better if it can automatically test the results of that on a production workload.
Or suggest schema changes that would improve normalization or performance.
Re: Ideas to improve the user and developer experiences of databases
#7I big red background when you are connected to production. I know it's bad practice, but don't pretend it doesn't happen.
Re: Ideas to improve the user and developer experiences of databases
#8I’d like a tool that automatically suggests which indexes to add/remove, including use of different types of indexes and partial indexes, based on the queries being performed. Even better if it can automatically test the results of that on a production workload. Or suggest schema changes that would improve normalization or performance.
RavenDB (1) got you covered but it's a document database. It automatically creates indexes and has a lot of built-in features to improve operability.
Re: Ideas to improve the user and developer experiences of databases
#9I played around making a stupid thing a bit like sqlfiddle but it would animate the executuon plan to visually show how rows were joined etc. (Say showing 10-20 rows of data at each stage), could also show stats for full dataset being processed.
I thought it would be handy for those learning sql, but i dont think its a pro tool.
In anycase i am mainly posting this comment as it seems a simple thing to do but ive never seen another tool that does it.. maybe if i had taken the project a few steps further i would have found a reason its a terrible idea.
Re: Ideas to improve the user and developer experiences of databases
#10Being able to write FROM table SELECT xxx instead of SELECT xxx FROM table (just like with relational theory, and to have autocompletion that works) would be just great!