4 ms·
One of the Bytebase authors here and I am the one who chose SQLite in the first place. The project started in 2021 Jan and I did notice litestream. And actuall
by tianzhou 5y ago
One of the Bytebase authors here and I am the one who chose SQLite in the first place.
The project started in 2021 Jan and I did notice litestream. And actually, one of the main reasons I chose SQLite is because of litestream. Because I could see it could be our HA solution when needing it.
SQLite is great, but the schema change constraint is really painful as you mentioned.
As to the Tailwind, as a backend engineer working on database for most of my 10+ career and single-handedly built the site, I can only say it's godsend;)
- no_wizard 5y agoCompletely unrelated to the thread, but the graphic on your home page doesn't quite re-size correctly, at least in the latest version of Firefox. It blocks the star button at i'd say tablet -> desktop range (somewhere between full width and not quite tablet) if you go smaller, it does at certain sizes block a bit of the text. tl;dr it doesn't look like the main graphic on your home page handles fluid layouts EDIT: this goes with a few other graphics on the front page as well. I also noticed some of your copy doesn't read well grammatically. "For Developer" I think reads better as "For Developers", as an example. Only mentioning this cause this is a really cool concept that I wish I had thought of years ago when I worked more heavily with databases and want you to succeed! One of the reasons ORMs are "nice" is the built in schema migration of a lot of the most mature ones (coming from .NET and previously Django). This is a similar idea, but for teams that need high performance SQL optimizations to be able to change schema that may be written against "raw" SQL / Window functions etc.
- tianzhou 5y agoThanks for the feedback and the encouraging words. I did try, but front-end development is harder for a database engineer... Definitely could be improved here.
- born-jre 5y agoany plan to maintain this[0] as separate library so anyone can embed pg in go binary? [0] https://github.com/bytebase/bytebase/tree/6a72eb630c604e2fe71de207a92a7db807261f09/resources https://github.com/bytebase/bytebase/tree/6a72eb630c604e2fe7... edit: there is already sth like that https://github.com/fergusstrange/embedded-postgres https://github.com/fergusstrange/embedded-postgres
- ochoseis 5y agoThe bottom of the article states: > Bytebase offers a web-based collaboration workspace to help DBAs and Developers manage the lifecycle of application database schemas. So, I guess it’s not surprising you’d be annoyed by not being able to change schema constraints :)