AI can write SQL. But can it actually understand your data? ๐
@Vikram_AI_1.6K followers
13,698 views
39 Comments
Comments from the original post on X (Twitter)

@AiwithDharmik
SQL is only part of the problem. Data understanding is what matters.
2 likes

@Vikram_AI_
getting agents to actually understand the semantics is where the real battle is. thanks for feedback

@VibeCoderOfek
dex gives the agent the schema. what happens when the warehouse changes the column name overnight
1 like

@silic2023
โActive customerโ is a good example of why schema alone isnโt enough. Two perfectly valid queries can disagree because one counts logins and another counts purchases. Making that definition visible beside the answer would help people challenge the meaning, not just the SQL.
1 like

@mmisbbahh
catching expensive queries before they run is the real win here, agents will happily full scan a 2tb table to answer a yes or no
1 like

@nahid_tech
This is a great step forward for AI-powered data engineering! Giving AI agents proper data context instead of letting them guess can make a huge difference in accuracy, efficiency, and reliability. Open source makes it even better! ๐ฅ๐
1 like

@itmagiber
amazing share
1 like

@Worldwide2060
AI writing SQL was never the hard part โ understanding the warehouse is. Blind SQL is how you get queries that run fine and answer the wrong question. Giving agents real context about the data is the fix that actually matters. Is Dex open for anyone to try on their own warehouse?
1 like

@pushkersoni72
amazing
1 like

@Arj_786
This is super cool! Giving AI the context it needs makes so much sense. Definitely going to check this out.
1 like

@balance0014
does Dex pick up dbt docs too, or just the raw schema? column names alone rarely tell you which table is stale
1 like

@heyrohitai
I like that the context lives alongside the models, congrats for launch
1 like

@Vikram_AI_
Appreciate it @heyrohitai keeping it right alongside the models makes the workflow so much cleaner. Try : also share with your network๐

@promptparag
Can Dex also help with complex joins across multiple schemas?
1 like

@stevencheng
Context beats guessing. My agents still hallucinate column names without it.
1 like

@Abhinavs1920
a query can run perfectly and count every customer twice. table names aren't enough, the agent needs the grain of each table... what if data is too big? will do hands on.
1 like

@Tanaypawar27
Really interesting project, especially for dbt users.
1 like

@Vikram_AI_
Yaaa exactly

@Awesome_O_AI
Giving AI coding agents real context about your data warehouse instead of letting them guess SQL is a smart idea
1 like

@Vikram_AI_
Exactly, blindly guessing schemas always ends up in broken queries. Check out Dex for more:
1 like


















