ndm | : computer : npm desktop manager https : //720kb.github.io/ndm | Frontend Framework library

IBM has a utility on the mainframe that can probably do what your asking. The utility is called IEBPTCH (IEB Print Punch). The documentation is here

Its not automatic but could be easier than writing code. From the doc

You can use IEBPTPCH to print or punch all, or selected portions, of a sequential or partitioned data set or PDSE. Data can also be "printed" or "punched" to disk or tape.

IEBPTPCH can be used to print or punch:

• A sequential or partitioned data set or PDSE, in its entirety
• Selected members from a partitioned data set or PDSE
• Selected records from a sequential or partitioned data set or PDSE
• The directory of a partitioned data set or PDSE
• An edited version of a sequential or partitioned data set or PDSE
• A data set containing double-byte character set data
• You can specify the format for the records that you are printing or punching, or you can use IEBPTPCH's default formats.

• The default formats are:
• Each logical output record begins on a new printed line or punched card.
• Each printed line consists of groups of eight characters separated by two blanks.
• Up to 96 data characters can be included on a printed line.
• Each punched card contains up to 80 contiguous bytes of information.
• Characters that cannot be printed appear as blanks.
• When the input is blocked, each logical output record is delimited by "*" and each block is delimited by "**". Sixty lines per page will be printed.

See the RECORD statement here

As linked in the comments, by default the paginator only allows sorting on columns that exist in the main table, columns of other tables (joins) or computed columns must be explicitly allowed via the sortWhiteList option.

The missing parentheses in the the generated window function SQL looks like a bug, the SQL Server query translator doesn't check whether the expression that is defined in the order clause is a query, which would require to wrap the generated SQL in parentheses.

I've pushed a possible fix for 3.9 and 4.1:

https://github.com/cakephp/cakephp/pull/15165
https://github.com/cakephp/cakephp/pull/15164

If you cannot upgrade right now, a possible workaround could be to wrap your subqueries in additional expressions, which when compiled should wrap the inner query expression in parentheses:

Generally if you need to format the results in some way, you should most likely use a result formatter, in order to be able to keep query object intact, and rom looking at the resulting format that your function produces, that is what you should use in this case, a result formatter.

If you need the ordering you could do that on SQL level already, and for nesting the results you could use the result collection's nest() method, ie you could ditch using the Hash class:

Try find the element with xpath, and get the title by .text like below:

The last suggestion of ndm made the trick. Now it works like expected. Thank you very much!

Here is the correct setup:

ProjekteTable.php

We can create a key column combining qseqid and sseqid and then select those assemblyName who either have more one distinct value of key or have only one row in them.

You could convert the table to dataframe and paste the column names in each row which has 1 as value in them and count their occurrence using table.

The docs seem outdated, as of CakePHP 4.x button contents are HTML entitiy encoded by default. From the migration guide:

Cake\View\Helper\FormHelper::button() now HTML entity encodes the button text and HTML attributes by default. A new option escapeTitle has been added to allow controlling escaping the title separately from other HTML attributes.

So you need to explicitly disable escaping (which requires using false, not true). 4.x also introduced the escapeTitle option, which you should use instead of escape, as the latter now only applies to HTML attributes:

You can aggregate and do conditional sums. Consider: