9 | Query problem after transaction commit records but only the latest stored record. I tried to run database explorer on the server machine ... explorer on the server, my client program can retrieve all the records (no program restart or ... printing result 41> UI: start query [database explorer started on server before the execution |
9 | Problem with 'where' and date()Hi, Today I was playing with some date-range queries in explorer and found a small problem ... . There is no such problem in code because we can set Date() object as parameter. However this is hard in explorer ... in the Explorer by using date literals. For example: SELECT o FROM TestObject o WHERE o.date > {d |
9 | @Transient, and then when I open the database in the explorer I see the ´boolean searched´ attribute in the object browser. See attached screenshot. I did not expect to see the searched attribute in the explorer´s ... for the Agency class maybe you can see what I am doing wrong? wlboluyt Will Boluyt The Explorer |
8 | ObjectDB version 2.3 has been released to edit databases in the Explorer (issue #2). Added the ability to execute queries in the Explorer (issue #3). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added ... !!! New explorer looks cool. Great work! lwalkowski Lukasz Walkowski Thanks. That was essential |
8 | Drop in Client/server mode not working your example at it works as long as the Explorer is not connected to the database. ie: If explorer ... , this is a bug in the drop feature, as it's important to be able to have the explorer open during testing ... . The Explorer is like any other database user so a database cannot be deleted while it is open |
8 | Running doctor.jar with entity classes in classhpath instances of these entities to database through explorer. I tried to run com.objectdb.Doctor with model ... explorer). Could it be possible to add that kind of feature in next relase ? I run doctor by ... , you can follow these 2 steps: Run the Explorer with the new class in the classpath: java -cp |
8 | ObjectDB is opening too many sockets lines the first one is TCP connection from explorer. This disappear when explorer is closed (or File ... Server, and did all connections from explorer only. I was working with 2 DB files (firstdb and seconddb ... running ObjectDBServer without restarts, also explorer was single instance, just closing |
8 | possible index required for improving query performance Explorer with a non-null parameter. If I run it with null, I can see in Explorer that it looks ... You should be able to use object parameters in the Explorer, as explained in the manual: In the [Parameters] table ... . It will be easier to explore this if the query can be run in the Explorer, so please suggest |
7 | Listing large number of complicated objects with paging. times in a row cause java.lang.OutOfMemoryError: Java heap space exception. The same query in Explorer runs blazing fast (22ms) but I think it's because Explorer lazy loads all that objects and load ... (and therefore completes in 22 ms in the Explorer). The problem is probably with the extensive EAGER |
1 | ObjectDB 2.8.4 unsupported unwrap to throw _PersistenceException (a subclass of PersistenceException). Fixed an Explorer bug in presenting composite IDs. Fixed a bug in using date and time query parameters in the Explorer ... objects in the Explorer (feature request #2602). Fixed a performance issue in viewing class |
