aquameta

> Feature Requests > Concerning schema changes: they desire PostgreSQL to record a history of schema change events, such as adding or removing columns and other DDL operations. You can do this right now today by using `EVENT TRIGGER`s. You can check out things like Aquameta[0] (if I remember correctly) to see how it's done. [0] https://github.com/aquametalabs/aquameta

Aquameta has an interesting extension that something like this in a different way: https://github.com/aquametalabs/aquameta/tree/master/extensi....

Related: "Web development platform built entirely in PostgreSQL" - https://github.com/aquametalabs/aquameta

Whoa, this project looks really cool. I'm trying to read the docs though, and there's a lot of broken links — e.g. all the "Backend Documentation" links here: https://github.com/aquametalabs/aquameta/tree/master/docs

Check out Aquameta, a web dev stack built entirely in PostgreSQL (self-plug): http://github.com/aquametalabs/aquameta There's a ton down this rabbit hole. One of the great anomalies of our industry is that we've used the database to bring coherence to countless "user domains", but never applied the same principles to our own stack. The benefits of doing so compound exponentially.

Has anybody seen any work where CRDTs get insight into conflict resolution using the underlying grammar of whatever text is being written (aka English, Javascript, regex, etc.)? Seems like the conflict resolution could do a better job if it knew the EBNF of the text that was being edited. Also, any prior art on CRDTs over relational data? I suppose each single field would potentially be an "editable space", but on a long document (say a Javascript code block), updating the whole thing in the db by overwriting it with each edit would not be very efficient. Seems like there could be a datatype that was a little smarter than "text", that could handle more granular updates, that implemented a CRDT index under the hood? I'm working on a VCS for relational data [1] which is more on the not-so-realtime-collaborative-editing end of the spectr

Ahh okay, that makes sense. I wasn't aware that using different methods of copying + backing up data had tangible effects on it later. Super interesting, and vital if you're looking to gather accurate data from experiments. By the way, I recognized you guys from the other tool you publish, Nancy. While I don't have a direct usecase for it myself, I thought the idea was super valuable as well. I am a huge Postgres guy (did you know you can build an entire web app in JUST Postgres?[0]) so I had bookmarked a couple of your projects. Thank you for the response, you guys do some fantastic work. [0]: https://github.com/aquametalabs/aquameta

There's broken link in your article to https://github.com/aquametalabs/aquameta/tree/master/core/00...

Kinda like aquameta[0]? [0] https://github.com/aquametalabs/aquameta

I'm keeping an eye on https://github.com/aquametalabs/aquameta "Web development platform built entirely in PostgreSQL"

Not what you asked for, nor is it ready to use, but Aquameta may be interesting to you considering your high-level goal: https://github.com/aquametalabs/aquameta.