Wow, what good news! I totally love Hasura but totally missed a lot of things since graphql. My stand was, that i don't want to use a second product for vectors and i'm totally into postgres and hasura.
My question: do the newly added hasura features make it completely obsolete to add pgai as extension to postgres or can they play along nicely.
My first guess is i'll simply combine both. I want to have a stack i can work and get deeply fimilar with and not change it all 3 month, when a new funky vectordb is announced.
My plan was to add: pgai
I came along a blog post from timescale last week, it's worth a read: https://www.timescale.com/blog/vector-databases-are-the-wron...
My question: do the newly added hasura features make it completely obsolete to add pgai as extension to postgres or can they play along nicely.
My first guess is i'll simply combine both. I want to have a stack i can work and get deeply fimilar with and not change it all 3 month, when a new funky vectordb is announced.