create-module-queries

To generate ModuleQueries.xml for a Directum RX module, you specify the required SQL queries and database engines. The tool outputs a correctly structured file at {ModuleName}.Server/ModuleQueries.xml containing properly parameterized SQL and correct XML escaping.

Writing parameterized SQL queries for PostgreSQL and MSSQL in Directum RX requires engine-specific variants within ModuleQueries.xml. The tool generates properly parameterized SQL adhering to engine-specific naming conventions for both database platforms.

Yes, you can use complex SQL patterns like CTEs, window functions, JOINs, aggregations, and temporary-table logic in Directum RX module queries. The tool supports DB-specific optimization for complex querying when generic LINQ queries are insufficient.

The best way to handle database-specific SQL optimization in Directum RX is creating ModuleQueries.xml with PostgreSQL and MSSQL query variants. This approach enforces Directum query conventions and required naming rules to maintain consistency across DB engines.

You need ModuleQueries.xml when LINQ or generic queries are insufficient for complex database logic. It enables JOINs, aggregations, window functions, CTEs, and temporary-table workflows where standard Directum RX queries fail to meet performance needs.

Yes, Directum RX requires correct XML escaping for module queries to ensure valid file structure. The tool automatically produces properly parameterized SQL with correct XML escaping and engine-specific naming conventions within the ModuleQueries.xml file.