# Suddenly, Rows Can Now Have Meaning

**URL:** <https://air.tableforums.com/t/suddenly-rows-can-now-have-meaning/386>\
**Category:** Airtable Developers\
**Created:** [March 9, 2023, 1:32pm UTC](https://air.tableforums.com/t/suddenly-rows-can-now-have-meaning/386 "2023-03-09T13:32:19Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![bfrench](https://yyz1.discourse-cdn.com/flex029/user_avatar/air.tableforums.com/bfrench/32/46_2.png) [@bfrench](https://air.tableforums.com/u/bfrench)\
**Post date:** [April 13, 2023, 12:36pm UTC](https://air.tableforums.com/t/suddenly-rows-can-now-have-meaning/386/9 "2023-04-13T12:36:47Z")

</div>

Yet [another interesting comment](https://community.airtable.com/t5/development-apis/suddenly-rows-can-now-have-meaning/m-p/150775/highlight/true#M12294) from afar, this time from afar.

My thoughts (seem to be inline with the creators thoughts):

1. This is a good learning moment.
2. It costs about a half-a-buck per search; an embedding architecture would be about 1/60th of a penny.
3. It is slow; search should be [Doherty threshold](https://lawsofux.com/doherty-threshold/) or less.
4. It replicates a lot of information in adjacent fields.
5. It’s an impressive array of steps; a Make posterchild for complex solutions.
6. Proof that if it can be done, it should not necessarily be done.
7. [Embeddings](https://air.tableforums.com/t/suddenly-rows-can-now-have-meaning/386); 'nuf said.

[![](https://canada1.discourse-cdn.com/flex029/uploads/tableforums/original/1X/af68ceebf403cb0e4cef1fd49d61b0ec30e7283d.jpeg "GPT-4: Unlocking Insanely Powerful Semantic Search for Airtable!") ](https://www.youtube.com/watch?v=ypbWestzDIo)

---

_[View the full topic](https://air.tableforums.com/t/suddenly-rows-can-now-have-meaning/386)._
