Please let me supplement a little. This library is intended for batch processing. "Carbunql" is a bit similar to LINQ in the areas it covers. It is the same a

Please let me supplement a little. This library is intended for batch processing. "Carbunql" is a bit similar to LINQ in the areas it covers. It is the same as LINQ in that SQL can be written in C#. I don't think there is any advantage to using "Carbunql" for this purpose. However, I thought that it would be useful in the following environments, so I developed it. - Writing SQL directly is more maintainable than using LINQ - You want to reuse that SQL for processing such as obtaining the number of records, adding dynamic search conditions, and creating a temporary table. - The overhead of SQL parsing is acceptable. In other words, the SQL execution frequency is low, and the parse waiting time is extremely small compared to the SQL execution time. the above is very special It may sound like it, but I think it's a common case in batch processing. In other words, I think that it is useful in batch processing.