Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

Changelog v3.4.6 (2025-01-21)

Version 3.4.6 (2025-01-21)

Full Changelog

Endpoint Execution Performance Optimizations

Reduced memory allocations and CPU overhead in the hot path of endpoint execution through several optimizations:

StringBuilder Pooling

Added a thread-safe StringBuilderPool to reuse StringBuilder instances across requests instead of allocating new ones:

  • cmdLog - command logging
  • cacheKeys - cache key building
  • rowBuilder - response row building
  • compositeFieldBuffer - nested JSON composite handling
  • commandTextBuilder - SQL command text building

The pool maintains up to 64 instances with lock-free rent/return operations.

Avoid Query String Dictionary Allocation

Changed from context.Request.Query.ToDictionary() to using IQueryCollection directly, eliminating a dictionary allocation on every request. The IQueryCollection interface already provides TryGetValue(), Count, and ContainsKey() methods.

StringBuilder for Command Text Building

Replaced ~18 string.Concat(commandText, ...) calls with StringBuilder.Append() operations, reducing intermediate string allocations when building SQL commands for non-formattable routines.

HashSet for Path Parameter Lookup

Added FindMatchingPathParameter() method with lazy-initialized HashSet<string> for O(1) case-insensitive lookups instead of O(n) array iteration when matching path parameters.


Comprehensive CancellationToken Propagation

Improved cancellation token propagation throughout the entire request pipeline. The CancellationToken parameter is now properly passed to all async operations, enabling proper request cancellation and resource cleanup when clients disconnect or requests are aborted.

Changes:

  • NpgsqlRestEndpoint: Fixed missing cancellation token propagation to ReadToEndAsync, ReadAsync, WriteAsync, FlushAsync, BeginTransactionAsync, CommitAsync, and helper methods (PrepareCommand, OpenConnectionAsync, ValidateParametersAsync, ReturnErrorAsync).

  • Auth Handlers: Added CancellationToken parameter to BasicAuthHandler.HandleAsync, LoginHandler.HandleAsync, and LogoutHandler.HandleAsync. All database operations and response writes now respect cancellation.

  • Upload Handlers: Updated IUploadHandler.UploadAsync interface and all implementations (DefaultUploadHandler, FileSystemUploadHandler, LargeObjectUploadHandler, CsvUploadHandler, ExcelUploadHandler) to accept and propagate cancellation tokens to file I/O and database operations.

  • Proxy Handler: Added CancellationToken parameter to ProxyRequestHandler.WriteResponseAsync for cancellable response body writes.

Benefits:

  • Immediate cleanup when HTTP clients disconnect mid-request
  • Proper cancellation of long-running database queries
  • Reduced resource consumption from abandoned requests
  • Better handling of upload/download operations that can be cancelled
  • Prevents request storms: When users repeatedly refresh the browser during slow endpoint execution, each refresh creates a new request while the previous one continues running. Without proper cancellation token propagation, these abandoned requests continue executing database queries, potentially choking the database. With this fix, abandoned requests are properly cancelled, freeing up database connections immediately.

Comments