In my first post about TypeSafe and Jev in .NET, I used the SDK to make structured judgments about text and JSON: Noul for a yes-or-no probability, Choice for an unordered selection, and Score for an ordinal rubric. In the follow-up about the MCP server, I showed how to make those same judgments available to an AI coding agent.
TypeSafe's JavaScript SDK v0.7.0 adds experimental image input and a box question type. "I" ported those features to my community .NET SDK in its own 0.7.0 update. The version numbers match, but these are separate releases: TypeSafe published the JavaScript SDK v0.7.0 on October 14, 2026, while the .NET SDK remains an unofficial community port.
Deadlock or just a queue? Three sessions are waiting. Name the two stuck together without blaming the third.
A waiting session is not automatically a deadlock. That distinction matters when the phone rings and everyone is looking at a diagram with too many arrows. Some waits clear as soon as the session ahead finishes. A deadlock is different: the waiting forms a cycle.
In the picture, teal arrows mean HOLDS and red arrows mean WAITS FOR. Session A holds resource X and wants Y. Session B holds Y and wants X. Session C wants X but holds neither resource in this drawing. Look at the arrows and ask which sessions would remain stuck if nobody intervened. Take a moment before you read the answer; the extra session is there to make you work a little.
The labels are deliberately simple. There is no hidden isolation level or lock mode to guess. This is a graph puzzle about the shape of the wait, not a complete SQL Server deadlock report.
Deadlock or Just a Queue: The Answer
A and B form the deadlock. A cannot get Y until B lets it go. B cannot get X until A lets it go. That is the cycle. C is waiting for X, but C does not close a cycle; it is in the queue behind the trouble.
SQL Server detects deadlocks and chooses a victim so work can continue. A long wait by itself does not prove the same condition. The next time you read a deadlock graph, follow the ownership and requests around the loop before you decide which statement deserves your attention.
This is why I like drawing a problem before naming it. If three people are waiting, 'three-way deadlock' sounds dramatic, but the arrows may say something much smaller. Here the right explanation is two sessions in a cycle and one bystander.
The diagram is intentionally a toy. Real deadlock reports include more detail about processes and resources. The useful question remains the same: where does the wait circle back? Once you can point to that circle, you can start asking why those transactions took the locks in that order.
AI in production without a second pair of eyes is a quick way to lose a table. Cardinal was going to add the WHERE clause. Eventually.
Cardinal Rules. A Saturday cartoon about AI and databases.
Every DBA carries the same scar. Somebody ran an UPDATE or a DELETE while the WHERE clause was still being typed, and the keyboard turned out to be faster than the thought.
What is new is the speed. Cardinal produces a complete, confident, perfectly formed statement before you have finished reading your own request. The pause where a person squints at the screen was the safety feature, and it is precisely the part that got removed.
Three things cost nothing and prevent the whole story. Give the assistant a login that can read and nothing else, so the worst case is a slow query instead of an empty table. Wrap anything that changes data in an explicit transaction, check the row count, then commit. And type the WHERE clause before the verb, because a half finished SELECT is harmless and a half finished DELETE is a resume update.
The VP is not wrong to want the speed. Writing the statement really is the slow part of the job for most people, and handing that over is a genuine gain. Pressing the button was never the slow part.
Cardinal can hold the pen. Somebody who will still be here on Monday holds the password.
Cardinal Rule
Type the WHERE clause first, especially when you are fast.
Read only login, explicit transaction, row count, then commit.
The Security Update for SQL Server 2025 RTM CU9 is now available for download at the Microsoft Download Center and Microsoft Update Catalog sites. This package cumulatively includes all previous security fixes for SQL Server 2025 RTM CUs, plus it includes the new security fixes detailed in the KB Article.
Log in
(@sergeytihon.com)
