chrstr

6 ms·

1.
by chrstr 2y ago
Well, Rust is great and everything... but calling DuckDB "the previous generation of data engineering" seems a bit funny. And if anything, DuckDB will probably have more impact than all the other mentioned tools (or maybe it even
2.
by chrstr 2y ago
I've built a similar board some time ago, focus was also mostly amateur level. It does include some of the mentioned features, i.e. it has a timeline to save different formations and graph connections (they don't move together tho
3.
by chrstr 2y ago
But curating such a list of experts to follow takes quite some effort. It would be great to have a tool that helps with that. And sure, ideally you wouldn't need such a list of trusted experts but just focus on content. There even was
4.
by chrstr 4y ago
CREATE TABLE data_a AS (SELECT 'a' AS test_case, 1 AS value); CREATE TABLE data_b AS (SELECT 'b' AS test_case, 2 AS value); CREATE VIEW data AS (SELECT * FROM data_a UNION ALL SELECT * FROM data_b); CREATE VI
5.
XGBoost Predictions Written in SQL(foldl.de)
2 points by chrstr 4y ago|0 comments
6.
by chrstr 4y ago
create table x as (select * from person); select name from x where ...; there you go, just configure your editor to display "create table x" as "declare x = " ;) or even a version with lazy evaluation: crea
7.
by chrstr 4y ago
Thanks! May be helpful to include this in the documentation, since I guess it will then often depend on the numDistinctRows estimate [1] if the parallel plan is used. [1] https://git.postgresql.org/gitweb/?p=postgresq
8.
by chrstr 4y ago
> Queries using SELECT DISTINCT can now be executed in parallel. This sounds quite interesting, but I would assume it does not always work? I didn't see this mentioned in the linked documentation, does someone know when/how the
9.
SQLite: Past, Present, and Future(vldb.org)
282 points by chrstr 4y ago|143 comments
10.
by chrstr 4y ago
> However, the term "Data engineer" was specifically created by/for ML folks to get rid of unpleasant repetitive work that has to be done but nobody looks forward to it. This may indeed be how the term "data engineer&
11.
by chrstr 5y ago
Indeed, it is generally good for analytics to have a conceptual data model that is reasonably efficient both on the technical side (to quickly get answers for queries), and also on the logical side (to quickly translate questions to queries
12.
by chrstr 7y ago
similar for Redshift: https://crst.github.io/vrqp/vrqp.html
13.
Redshift Query Plan Visualization(crst.github.io)
2 points by chrstr 7y ago|0 comments
14.
Dense timeline charts for event logs(foldl.de)
1 points by chrstr 8y ago|0 comments
15.
An easy way to find redundant edges in a DAG(foldl.de)
2 points by chrstr 8y ago|0 comments
16.
XGBoost predictions with PostgreSQL(foldl.de)
2 points by chrstr 8y ago|0 comments