1,400 karma · joined October 14, 2010
using the "RPLidar A2" https://www.slamtec.com/en/Lidar
looks interesting.
I wonder if the authors are aware of http://hjson.org/. It has similar features as far as loosening the json syntax rules and a lot of client libraries. HOCON seems to go a lot further in features/complexity.
Also worth noting: "Discretionary spending limits, addressed by this proposal, are set by congressional budget resolutions. Congress typically makes changes to the president’s proposal — last year, lawmakers disregarded Obama’s budget altogether. "
https://www.washingtonpost.com/graphics/politics/trump-presi...
The last blog post from 2017-Jan-10 says "I’m pleased to announce that we are starting to test the first usable version of Pijul.We are not quite ready to release.."
I was hoping that getting to the front page meant pijul had done a release but I see nothing to that effect.
It was working with ruby on rails that taught me one of the strongest reasons to use psql over over databases - transactional schema changes. If a migration fails I absolutely want the whole migration rolled back so that the schema can be fixed and tried again.
Which is why this paragraph is alarming:
"First Flyway now autodetects whether a non-transactional statement is present within a migration. If it is, then the whole migration is run without a transaction (and clearly labelled as such in the logs)."
Arguably, mostly devs working with psql dont know that its possible to create schema change commands that cannot be transactional, myself included. I imagine creating such a statement 'by accident' is exceedingly rare, but a default of allowMixedMigrations to false seems more sensible to be 'default safe'. I say 'safe' because a broken, half-executed migration can leave a real mess.
Thanks for your efforts and for the flyway project!
best self-driving comment ever.