Recent submissions

Comment · 2 years ago
How does it handle large schemas? A quick schema dump shows that we have around 100K columns between all of our tables. Say we use 10% of that.

How easy is it to select which tables should be taken into account?

Is there an intermediate context layer step to work with this?

Do you need to provide working examples for the tool to know how joins and relations are usually handled?

Comment · 2 years ago
Cant get this to work. Instructions are very unclear. Was unable to open a snowflake connection. Uploaded schema in a csv file. No indication of what needs to be done next. Assume that manage context queries is where it pulls info from. Added a query and provided a dsecription. Tried Q&A, nothing happened
Comment · 5 years ago
Hot air goes up
Comment · 5 years ago
A good interest rate in Mexico is 9%, with the most common form of mortgage being around 12%
Comment · 5 years ago
Same, for me, being able to use two languages at the same time is critical. But don't ever see myself paying monthly for a keyboard
Comment · 6 years ago
Basically you make keys out of your data:

| Week# | clientid | key |

| W01 | CLI001 | CLI001W01|

You use this newly created key to match data on your databases/files

Comment · 7 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton