Hydrocharged

5 ms·

1.
Is Postgres Too Customizable?(dolthub.com)
1 points by Hydrocharged 2y ago|0 comments
2.
Exploring DoltgreSQL Through Type Compatibility(dolthub.com)
2 points by Hydrocharged 2y ago|0 comments
3.
by Hydrocharged 3y ago
You can think of Dolt as having 4 layers to it. From the top-most interface to the bottom: Vitess (Handles Wire Protocol) go-mysql-server (GMS, Implementation of MySQL featureset) Dolt GMS interface Storage Engine DoltgreSQL, right now, sha
4.
by Hydrocharged 3y ago
The sqllogictests are better used as a judgement of how accurate our results are to MySQL's results given a very large range of statements (around 6 million tests). They are not, however, indicative of the entire feature set. That&#x27
5.
by Hydrocharged 3y ago
Thank you! :D
6.
by Hydrocharged 3y ago
This is a fully-versioned database. By versioning, think of how Git applies to text files, and all of the power that comes from that model. You have branching, diffing, merging, etc. It allows you to collaborate with each other, or you can
7.
by Hydrocharged 3y ago
You understood correctly! That's just one use case, there are many, many more. Some of which we haven't even considered yet, just because the model is that powerful.
8.
by Hydrocharged 3y ago
hahn-kev made a really good comparison, but it can go a step further. Not only can you query the data at some previous point in time, but you can even run a join across old and current data. If you look at it from the perspective of commits
9.
by Hydrocharged 3y ago
Just want to point out that we're announcing development on the project. It's absolutely not ready for mainstream use yet! We have Dolt ( https://github.com/dolthub/dolt ) which is production-ready and widely i
10.
by Hydrocharged 3y ago
The engine is free and open-source. You can buy support, but these are free products. https://github.com/dolthub/dolt In fact, we've got a blog post about Dolt and Wordpress. https://www.dolthub.com&#x2
11.
by Hydrocharged 3y ago
At the moment, it does not exist for DoltgreSQL as it is in pre-alpha. Dolt ( https://github.com/dolthub/dolt ), however, may be a better fit for your use case. https://docs.dolthub.com/concepts/dolt
12.
by Hydrocharged 3y ago
Dolt was built with MySQL in mind, and we're creating DoltgreSQL with PostgreSQL in mind. We've gotten interest in a "Dolt for Postgres", and so we're finally starting development on that exact thing.
13.
by Hydrocharged 3y ago
Knowing that extensions are very important to you is great feedback for us. As we hear more about what users' requirements are, it helps us better plan for the future. Regarding any differences from mainstream Postgres, you can look to
14.
by Hydrocharged 3y ago
I just learned of Neon a few weeks ago. From the looks of it, Neon supports branching, but it doesn't support merging. Xata supports both branching and merging, however it only applies to the schema. Dolt (and eventually DoltgreSQL) ha
15.
by Hydrocharged 3y ago
We've got a blog about a few use cases that you might find interesting. https://www.dolthub.com/blog/2022-07-11-dolt-case-studies/
16.
by Hydrocharged 3y ago
The adoption of Dolt has not pointed to this being the case. Many of our (paying) customers have not had PostgreSQL setups, and only around last year have we started to run into potential customers who truly needed a PostgreSQL variant of D
17.
by Hydrocharged 3y ago
This isn't a fork of PostgreSQL, it's a completely bespoke database solution. Its only tie to PostgreSQL is that we've chosen to appear as a PostgreSQL server to clients. If a user didn't use any versioning features, the
18.
by Hydrocharged 3y ago
This is interesting, I've never heard of VMDS before. Someone else on the team may have, but I have not personally. From a quick glance at the linked Wikipedia page, it looks like this was created around the same time as SQL, and there
19.
by Hydrocharged 3y ago
Thank you! Performance optimizations are tackled a bit differently than correctness ones. For the most part, we'll try to use metrics to find weak points in the execution graph and optimize those, but we won't go so far as to try
20.
by Hydrocharged 3y ago
In person, we generally say Doltgres, similar to Postgres. For the full name, it's just going to be Doltgres-Q-L.
21.
by Hydrocharged 3y ago
We don't really compete with Flyway and Bytebase. Schema migrations are but one aspect of a versioned database. We version everything , from the schema to the data. You can read more here: https://www.dolthub.com/blog&
22.
by Hydrocharged 3y ago
Back then, when we were surveying the landscape, PostgreSQL was definitely in widespread use, but we were seeing MySQL being used in more professional/non-hobby spaces. Nowadays that's not necessarily the case, and we are seeing s
23.
by Hydrocharged 3y ago
> Do you have a clear position on which PostgreSQL features not to support? I suppose there are more than just some things that won't make the cut because of the architectural decisions. While I unnderstand the decision, I'm n
24.
Show HN: DoltgreSQL – Version-Controlled DB, Like Git and PostgreSQL had a baby(github.com)
162 points by Hydrocharged 3y ago|63 comments
25.
Unlocking Time-Travel for Data and Code(dolthub.com)
2 points by Hydrocharged 4y ago|0 comments
26.
Changing SQL column types without rewriting every row in the table(dolthub.com)
1 points by Hydrocharged 6y ago|0 comments
27.
Foreign Keys in a Versioned Database?(dolthub.com)
1 points by Hydrocharged 6y ago|0 comments
28.
We implemented secondary indexes in Dolt, our version controlled database(dolthub.com)
5 points by Hydrocharged 6y ago|0 comments
29.
How we implemented MySQL types in our versioned database(dolthub.com)
5 points by Hydrocharged 6y ago|0 comments