Christopher Schultz

Yes, please. Using channel definitions with revision-control means this is a problem which turns small changes into huge-looking ones.

I think you want your index to contain message_id as well. Otherwise, it's just an INDEX on the column which still has to go to the clustered-index (or however the...

It also means that current code won't compile against older Mirth sources. Let's say you wanted to update your plug-in for Mirth 3.8.0 because it contains a bug of security...

I'm curious about this: > [...] there is already an endpoint that returns the server status (GET api/server/status) and when it returns `0` then the server has started. How are...

> @ChristopherSchultz Is there a list of supported database systems with which the DataSourceStore is compatible? Are you sure that they all support "SELECT FOR UPDATE"? I tried to look...

The problem is that there is a window of opportunity between the existing `DELETE` and `INSERT` where the `session_id` column (which is `UNIQUE` or equivalent) can be `INSERT`ed by another...

I've been thinking about this more and I think it could cause problems for people not using appId+sessionId (or just sessionId) as the primary key for the DB table storing...

> I have a question that why we don't add a real **primary key**(auto-increment) to solve the problem that primary key constraint violation when insert data to database simultaneously? The...

> I would love to see an interface that goes a step further and allows for NoSQL implementations as well. For example, Redis is an excellent option for a data...

> Punt the session update operation to a callback or interface, have one or two sensible defaults (like for the major databases and specific table configuration) and have a way...