deesix

VillageSQL extension for MySQL puts MCP on the database server.

Run duckdb queries over your S3 data and join with MySQL data in the same instance.

Code to create HNSW index:

CREATE TABLE demo_vectors ( id INT PRIMARY KEY, embedding SVECTOR(3) NOT NULL, INDEX idx_embedding (embedding hnsw_l2) USING EXTENDED(hnsw) ) ENGINE=InnoDB;

After years of MySQL development happening largely behind closed doors, Oracle has been making real progress towards making the MySQL project more open and community-oriented.

AWS announces they are on steering committee for MYSQL via blog post.

Oracle announces a new steering committee and governance model for MySQL.

There is now a Rust SDK for the VillageSQL fork of MySQL that allows you to write extensions in Rust, just like pgx/pgrx in PostgreSQL.

Founder here. Thanks for spending time with VillageSQL. Love all the feedback.

Ha! Founder here. Tell me why? Trying to make it easy, not be terrifying! I think the embed generation saves folks some steps.

Founder and CEO here. Great question. Right now, since you are linking MySQL files that means that all the extenions need to be GLPv2 or compatible license. In the future, we are hoping to have a stable SDK that is indepedent of the MySQL files so that if you run it out of process, that would give more licensing options to folks. There is a proof of concept of an out-of-process mode for the extensions in the alpha, but we haven't spent much time on proving it out.

With Bring-Your-Own-Media (BYOM), customers supply their own installation media and bring their SQL Server licenses to Amazon’s RDS Custom managed cloud service. RDS Custom for SQL Server is a managed database service which provides administrative access to the OS and DB configuration.

Disclosure: I work on GCP

Thanks for highlighting. We were aware of this and working with the local sales teams to make it as easy as possible.

Disclosure: I work on GCP

Thanks for the feedback. We spoke to number of existing GCP customers for feedback, but it's fair to say we can always talk to more non-customers.

Disclosure: I work on GCP

Thanks for the feedback. As the person that named both products, I can say we spent a ton of time debating this but we felt that the fact one is an enterprise file share and the other a document database service focused on mobile and web would mean very little conflict for customers. We will keep an eye on any customer confusion it might cause.

Disclaimer: I work on GCP

Can you point me to the complaints? I will take a look.

Disclosure: I work on GCP

To understand, what services got pulled? we have a very long deprecation policy and I can't think of anything that has been removed in the last couple of years.

Quick question. Which version of MySQL were you running? 5.6 is single thread on the slave and falls behind more easily. 5.7 gives you multiple threads and does a better job of keeping up.

Disclosure: I work on Google Cloud and Cloud SQL

Sorry, for any product on GCP, there is a 1 year deprecation policy. GCP isn't going anywhere. See the comment about Snap and Diane Greene's involvement (she is an Alphabet board member).

Disclaimer: I work on Google Cloud Platform

Two things:

1) Google Cloud Storage can host static websites:

https://cloud.google.com/storage/docs/hosting-static-website

2) Google Cloud Platform has a 1 year deprecation policy, which would never happen with a product that so many companies and customer rely on (Google Reader had a small but passionate base)

Disclaimer: I work on Google Cloud Platform

There is real work to migrate you application to use Cloud Spanner. Your schemas and queries will work with some tweaking but we don't have ORM support at beta.

We are going to produce some additional collateral on migrating from popular RDBMS, but the Quizlet post is the best reference right now for migrating from MySQL.

https://quizlet.com/blog/quizlet-cloud-spanner

We have released client libraries for Java, Go, Node and Python on Github, but we haven't used those clients to implement support for popular ORMs.

Basically, the open-source ecosystem will need to add support for these ORMs but we will contribute wherever we can to push these initiatives. If we get lots of demand for a specific ORM, we will look into doing something special for that.

Hope that helps.

(disclaimer: I work on Cloud Spanner)

Yes, it's something we have on the roadmap. We will adjust priority based on the level of demand so thanks for your vote ;-)

(disclaimer: I work on Cloud Spanner)

Just to be clear, the JOINS were removed for the vertical sharding prior to looking at Cloud Spanner. Cloud Spanner fully supports complex JOINS of many times (e.g. INNER, OUTER)

Details - https://cloud.google.com/spanner/docs/query-syntax#join-type...

Disclaimer: I work on Cloud Spanner

Yes. We are listening.

Disclosure: I work on GCP