bit.io

The immediately productive, shareable cloud database.

[bit.io @bitdotioinc]

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. https://t.co/n6nRIECPfM

[Danel Dayan @DanelDayan]

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

[Adam Fletcher @WriteAheadLog]

We're better at releases than you: https://t.co/HQwZeW4p0s
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, performance & reliability improvements, mobile support, and more.

[bit.io @bitdotioinc]

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

[bit.io @bitdotioinc]

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

[bit.io @bitdotioinc]

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.

[bit.io @bitdotioinc]

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

[Sam Lambert @samlambert]

It was good weather for a walk with @WriteAheadLog today.

[bit.io @bitdotioinc]

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

[Adam Fletcher @WriteAheadLog]

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

[Peter Zaitsev @PeterZaitsev]

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

[Tailwind AI @tailwindai]

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

[bit.io @bitdotioinc]

@yar_vol @alexgraveley @CockroachDB https://t.co/ZjMueuf014 supports pgvector!

[bit.io @bitdotioinc]

@GoogleColonizer @danjliden That said: the last thing we want is for the model to confidently answer an ambiguous question. Being able to flag ambiguities or at least provide an interpretation of the prompt before answering will be hugely beneficial.

[bit.io @bitdotioinc]

In our latest post on LLM text-to-SQL translation, we discuss how to test and compare task prompts/prompt templates—that is, how to make sure that well-constructed user prompts consistently lead to working SQL. We then compared #ChatGPT to Codex models.

https://t.co/yvKNsgfoNH

[bit.io @bitdotioinc]

@GoogleColonizer @danjliden In our limited testing of ambiguous prompts, LLMs have been pretty good at detecting ambiguities and can, if told to do so, ask for clarification. But users still have to ask the right questions. While LLMs can assist with SQL, they can't always rectify flawed logic.

[bit.io @bitdotioinc]

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

[bit.io @bitdotioinc]

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

[bit.io @bitdotioinc]

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

[bit.io @bitdotioinc]

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!

[bit.io @bitdotioinc]

We wrote about the process of switching from the Codex API to the ChatGPT API here:

https://t.co/LATClI3oLl

[bit.io @bitdotioinc]

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