About report generator

21-30 of 200Refresh
Result
12

ObjectDB Object Database Features [2018-10-27]

solution. General Highly optimized code (as a result of many profiling sessions). Unique data structures ... . Math: java.lang.BigInteger and java.lang.BigDecimal. Auto Value Generation Modes (for primary Key ... from a database snapshot. BIRT Reports ObjectDB databases are valid BIRT data sources. BIRT data sets can be defined using JPA and JDO queries (JPQL, JDOQL).  
Result
12

ObjectDB Object Database Features

). Performance and Speed ObjectDB is extremely fast - much faster than any other JPA solution. General Highly ... and java.lang.BigDecimal. Auto Value Generation Modes (for primary Key fields) Database IDs ... . BIRT Reports ObjectDB databases are valid BIRT data sources. BIRT data sets can be defined using JPA and JDO queries (JPQL, JDOQL).  
Manual
10

Database Doctor

, and if the file is not valid (it is corrupted), produces detailed diagnosis report of all the errors. Repair ... above) is the path to the new database file to be generated by the ObjectDB Doctor.
Forum
8

Error happened while running report.

occurred at preview result time. Like: org.eclipse.birt.report.engine.api.EngineException: Error happened while running the report. at org.eclipse.birt.report.engine.api.impl.DatasetPreviewTask.doRun(DatasetPreviewTask.java:330) at org.eclipse.birt.report.engine.api.impl.DatasetPreviewTask
Forum
8

Speeding up reporting queries with size() on list

Hi, I'm working on some reporting stuff in our application. One of few different reports should include activity on last modified objects. The query for now looks like this: select date(insp.lastModificationDate), insp.modifiedBy, insp.description.length(), insp.products.size(), insp.picture
Forum
7

ObjectDB's Database Doctor Incorrect Error Report

there will be a clear limit of 64KB. Thank you for this report. To avoid this error use page size of 64KB or
Issue
7

query only reports 1 result

, a number of them fit with the complete condition This is fixed now in build 2.7.2_02. Thank you for this report. it works, thanks hgzwicker
Issue
6

auto-generated uuid fields

Hello, we're porting a JDO application to ObjectDB which uses uuid-hex generated values. However the page on generated values in your JPA tutorial only mentions numeric generated values, and when we try to use it the error message seems to imply that auto-generating strings isn't supported
Forum
6

Possible issue for default id generator

generator when strategy is sequence. Error: Incomplete definition of auto value in field MyTestCase ... and 36: @GeneratedValue(strategy=GenerationType.SEQUENCE)//, generator="seq") @Id ... there is no default generator but the element generator is optional. Thanks. In ObjectDB using
Forum
6

auto-generated uuid fields

Hello, we're porting a JDO application to ObjectDB which uses uuid-hex generated values. However the page on generated values in your JPA tutorial only mentions numeric generated values, and when we try to use it the error message seems to imply that auto-generating strings isn't supported