this post was submitted on 14 Sep 2025
920 points (98.7% liked)
Programmer Humor
26875 readers
228 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had something similar to that with Power BI DAX where the same "intuitive" structure (a table definition) had different syntax for two similar purposes.
The inline table constructor for a single column table is
{value, value, ...}
, with the column just named "value". The constructor for a multi-column table is{(value, value, ...), (value, value, ...), ...}
, and the columns are named "value1", "value2" and so on.The function
DATATABLE
allows both specifying the column names and types for the data. The syntax for the data argument is{{value, value, ...}, ...}
.If you can spot the difference, you will have figured out why simply transplanting my constructor into a
DATATABLE
didn't work, but copying an example and replacing the values one by one did. It took me way too long.Maybe you just missed some nuance your brain skipped over?