Hi Trity, sorry it wasn't clearer. Generated Columns don't solve all data quality problems everywhere, it's just to make sure data matches between columns. Let's say my employee ID is my initials and the year I started; 'HS2019', and I want a second column that's just the year part. With generated Columns you're guaranteeing that the year part is *always* going to match the employee ID. Does that make more sense? Holly
The video is playing back strangely interlaced, like a column was out in the stream or what not.
are you hiring?
yes! check out databricks.com/company/careers
Honestly I did not follow. Too fast and the subjet of data quality is too important for this
Hi Trity, sorry it wasn't clearer. Generated Columns don't solve all data quality problems everywhere, it's just to make sure data matches between columns. Let's say my employee ID is my initials and the year I started; 'HS2019', and I want a second column that's just the year part. With generated Columns you're guaranteeing that the year part is *always* going to match the employee ID. Does that make more sense? Holly