 3 | -363f-4397-8553-cc5688ba142d')
ORDER BY MAX($1.createDate) DESC but this query returns ... ChatHistoryItem $1 JOIN $1.recipient $2
WHERE ($2.id='22afeafe-363f-4397-8553-cc5688ba142d') ORDER BY MAX ... ="desc(max(any(any($1.createDate))))">
|
3 | The application works fine with only 256MB heap size with objectdb 1.0 But on 2.0 even with max heap size ... " />
max="8mb" stdout="false" stderr="false" />
max="128mb" />
|
3 | error shown - ojectdb.conf is (we tried max-threads with 24, 40, 80, more or less the same result ... -history size="50" user="true" password="true" />
max="8mb ... " resize="256kb" page="2kb" />
max="96mb |
2 | processor cores. What is strange for us is that max 20% of the cpu resources are used and the IO subsystem ... path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> max="128mb |
2 | to get the object with the highest Id. I tried a query like "count(this.Id)" or "max(this.Id)" but I ... query, with very fast execution time. Similarly to get MAX/MIN values:
SELECT MAX(m.id) FROM MessageImpl m or in JDOQL (with a single query string):
SELECT MAX(id) FROM MessageImpl If the field |
2 | " user="true" password="true" />
max="8mb" stdout="false" stderr="false ... ="true" sync="false" path="." max="128mb" />
max-threads="10 |
2 | ="$objectdb/log/" max="8mb" stdout="false" stderr="false" />
max="128mb ... " />
max-threads="10" />
|
2 | /" max="8mb" stdout="false" stderr="false" />
max="128mb ... " />
max-threads="10" />
|
2 | -history size="50" user="true" password="true" />
max="8mb" stdout="false ... " />
max="512mb" />
max-threads="10" />
|
2 | mode="NON_XA"/>
max-entries="10000"/>
max-idle="100000"/>
max-entries="10000"/>
max-idle="100000 |
