Live data from Hacker News

Viewing profile — anze3db

anze3db

HN member
Joined
Wed, Dec 13, 2023, 4:01 PM UTC
HN karma
61
Public activity
37 items

About anze3db

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #40995307

    Great point. I thought that `vacuum into` blocks writes, but it's only `vacuum` that blocks! I've updated the blog post, thanks!

  3. comment
    Comment #40732945

    I'm in a few Discord servers, but I have no idea how to find you there :)

  4. comment
    Comment #40691599

    I agree 100% with everything you wrote. It was very surprising to me that every transaction and every write operation blocks the whole database and not only the table it's performe…

  5. comment
    Comment #40691536

    Don't get me wrong, the PR review is still rigorous and can take weeks. But everybody I interacted with during the process was very supportive and helpful, so the overall experienc…

  6. comment
    Comment #40691481

    Stephen has a whole series of blog posts on SQLite (in Rails) that I highly recommend. I've learned most of what I know about SQLite from him! https://fractaledmind.github.io/2024/…

  7. comment
    Comment #40689839

    From what I understand, you still need the experimental WAL2 mode[0] to not have this problem. [0] https://www.sqlite.org/cgi/src/doc/wal2/doc/wal2.md

  8. comment
    Comment #40689826

    While this blog post was at the #2 spot on HN it was getting 0.138 rps, so yeah 14k RPS is A LOT! That said it's still good to know when your tools will break! As far as I understa…

  9. comment
    Comment #40689051

    From what I know, the journal_size_limit PRAGMA still affects WAL mode, but it doesn't solve the issue of the WAL file potentially growing uncontrollably. Am I missing something?

  10. comment
    Comment #40689040

    I've heard this is a potential issue but I've never encountered it. Do you know about the experimental WAL2 branch[0] that splits the WAL file into two to circumvent this problem? …

  11. comment
    Comment #40688896

    I can confirm. My experience contributing has been very positive!

  12. comment
    Comment #40688753

    That's rough. Is your code using transactions? If so, making sure you use `begin immediate` will help!

  13. comment
    Comment #40688723

    I'm not a Django core dev, but I have managed to get my changes merged into Django already (the transaction_mode setting in 5.1 was my contribution). Carlton does seem to be onboar…

  14. comment
    Comment #40688597

    Hey HN! I'm the author of the blog post. I didn't mention this in the post, but I'll try to merge some of these settings into Django by making them the new default or the default f…

  15. comment
    Comment #39892125

    This joke makes some good points.

  16. comment
    Comment #39814915

    You've missed: pdm, uv, pip-tools, pipx, rye, and probably some others. Only pdm and poetry generate cross-platform lock files by default as far as I know, but there are a lot of p…

  17. story
  18. comment
    Comment #39389008

    I'm not sure if you can compare a project that came out of a university and got adopted by Apple with a project developed by a VC backed company with no revenue. I'm sure Charlie h…

  19. comment
    Comment #39388794

    If they stop development on Ruff today, Ruff won't be useful anymore after a few new Python releases. If the maintainers of the tools that Ruff is replacing stop maintaining them, …

  20. comment
    Comment #39388626

    What they are doing is already discouraging people from contributing to the projects their tools are replacing[0]. If they go out of business and stop supporting their tools, it mi…

  21. comment
    Comment #39388486

    I hope they answer this ASAP. People in the Python community are already concerned that Astral is following the Embrace, extend, and extinguish playbook.

  22. story
  23. story
  24. comment
    Comment #38980652

    I'd love to read your thesis! If it's possible please send a link :)

  25. story
    Show HN: Flakytest.dev – Improve your flaky test handling process

    I made flakytest.dev because I was frustrated with how teams usually handle CI failures due to flaky test (in my experience it's often a manual process). The core feature is a one-…