https://t.co/ZjMueufxQC is joining @databricks ! We are sunsetting our database product on June 29th. Check out our blog for more. Thank you to all of our users.

Good piece by @bitdotioinc on why we should care about vector databases. https://t.co/69KZPNRax2 h/t @WriteAheadLog @JMoMort

We're better at releases than you: https://t.co/y3oiVD20Xw Iteration speed & developer productivity is the biggest advantage of a startup. @bitdotioinc is 8 devs and in the last few months we've shipped: multi-region & multi-cloud, service accounts, text->SQL, new pricing,

Try it for free on https://t.co/ZjMueuf014. In our latest post in The Inner Join, we guide you through the process of getting vector embeddings from your documentation and conducting semantic search with bit.io+pgvector. https://t.co/hQtj818MTN

No need for specialized vector databases—with #Postgres and https://t.co/ZjMueuf014, integrate semantic search easily into your projects. Store vector embeddings and perform searches with the pgvector extension—all within your Postgres database.

Vector search enables powerful semantic search capabilities, for searching by meaning rather than keyword. It uses large language models, embeddings, and similarity metrics. Now, you can implement it in #Postgres using the pgvector extension. https://t.co/hQtj818MTN

Great to see this coming together of the #PostgreSQL and #mysql community.

In our latest post in The Inner Join, we show how to use the pgvector Postgres extension on https://t.co/ZjMueuf014 for vector similarity search—all in #PostgreSQL, no other specialized tools or integrations needed. https://t.co/hQtj818MTN

@alexgraveley Yep! I think we ( https://t.co/kgBXyHKGvp) are by far the least expensive & fastest way to use pgvector with Postgres.

ChatGPT writing SQL https://t.co/pMWCrcj1r1 #sql

@Exploringfornow Ouch ☠️ @bitdotioinc’s postgres database with pgvector works out much much cheaper at $5/month after a super generous free tier

LLMs, when integrated with other tools, unlock a world of potential applications beyond end-user text delivery. In this post, we provide some examples of how integrations with other tools can enhance text-to-#SQL translation. https://t.co/iOP9xQN0O2

Are you a #NodeJS developer? Take a look at our Node.js SDK for connecting to https://t.co/ZjMueuf014 databases and interacting with the https://t.co/ZjMueuf014 developer API. https://t.co/KDBgYQ104B

This is part of a series on our efforts to make the best production-ready text-to-SQL translation system. Keep an eye on this feed for all the updates: https://t.co/VV2ydSxwzb

We wrote about the process of switching from the Codex API to the ChatGPT API here: https://t.co/LATClI3oLl

With @OpenAI discontinuing the Codex API, you might wonder what's going to happen to our #AI text-to-SQL functionality, which is based on Codex. We'll be switching the system over to the #ChatGPT API in the next couple of days—you shouldn't notice any difference or interruption!

Now that @OpenAI is discontinuing its Codex API, you might want to switch to #ChatGPT for code completion. The chat-based API calls are different, but you can still get very good code completions. Here's one way to do it! https://t.co/LATClI3oLl

For a little more of the How and Why behind our new pricing, as well as some comparison with other pricing models on the market, read our blog post on the topic: https://t.co/YwR7DUbOlV

🚀 With a clear pricing structure based on row operations (reads/writes/updates/deletions of data rows), https://t.co/ZjMueuf014 aligns customer and provider incentives, so you can focus on what matters – building awesome products! 💡 Learn more:

🔥 We make it super easy to set spend limits, and with a continuously-refilling pool of row operations, your database stays available even when limits are reached. No more database downtime! Your https://t.co/ZjMueuf014 Pro database will always be available.