tkejser

5 ms·

1.
Is this why Spark users think joins are expensive?(floedb.ai)
1 points by tkejser 4mo ago|0 comments
2.
Data Modeling Blog Series(floedb.ai)
2 points by tkejser 5mo ago|0 comments
3.
by tkejser 7mo ago
That's fair feedback and I shall take that into account in future blogs. Thanks for letting me know - you can stare yourself blind on that stuff
4.
by tkejser 7mo ago
INFORMATION_SCHEMA is a good start, but it does not get you to full metadata flexibility. The columns you need just aren't there. It is good to have a standard for the metadata - but the standard isn't ambitious enough (a point I
5.
by tkejser 7mo ago
Merging to PostgreSQL core for something that needs to run on top of a Petabytes of data in the cloud, on Iceberg, with an advanced query planner and a high speed SIMD engine.... AND trying to squeeze into the "pg_" naming mess? I
6.
by tkejser 7mo ago
To clarify a point: We store the row count of each operator in the query - not the actual row (that would indeed be madness!). Though we DO have tracing you can control that allow you to enable rows for very specific diagnostics - but the s
7.
by tkejser 7mo ago
@da_chicken: You can read more about Snowflake ID in the Wiki page linked in the article. The short story: They are bit like UUID in that you can generate them across a system in a distributed way without coordination. Unlike UUID they are
8.
by tkejser 7mo ago
Thank you and yes! By making the entire architecture of the database visible via system objects - you allow the user to form a mental model of how the database itself works. Instead of it being just a magic box that runs queries - it become
9.
by tkejser 7mo ago
There are reasons for not USING. First, you need to be aware of the implicit disambiguration. When you join with USING, you are introducing a hidden column that represents both sides. This is typically what you want - but it can bite you. C
10.
by tkejser 7mo ago
I didn't really write USING in anger until around 10 years ago, and I have been around a long time too. Not all databases support it. But once you start using it (pun) - a lot of naming conventions snap into place. It has some funky se
11.
by tkejser 7mo ago
Hi All Original author here (no, I am not an LLM). First, a clarifying point on INFORMATION_SCHEMA. In the post I make it clear that this interface is supported by pretty much every database since the 1980s. Most tools would not exist witho