ObjectDB Database Search

, only one line, is always on the bottom. No more stack track ! gzdillon Lai Yang Maybe this is related

Hi, all:     This bbs is wonderful, clean, fast. But it has no REPLY button, that can add a hint to which message the author is reply.     Sometimes, multiple replies confuse us in tracking the discussing topic, if a hint like this will be good: On 5/13/2011 11:46

that the issue is hard to track . It must be a really small bug as it hardly ever happens (maybe

(as your description). This is because without enhancement tracking changes to objects at the time

.__odbWriteContent(MetaDataBean.java:1) at peoiws5. track .persistence.TrackMetaDataBean.__odbWriteContent

for every topic and use the issue tracking for clear ObjectDB bugs. Regarding logging - the ordinary

the Issue Tracking system to contribute ideas and suggestions. support Support

feature request if you need this functionality. Please add your comments regarding this feature (if any) in the issue tracking system. support Support

I'm trying to track down an issue in an application - the problem occurs around the retrieval of an object from a database the specifics are unclear at the moment. In the objectdb log the following message is written everytime the issue occurs. Could you give more detail about what this message

file size will divide that operations to smaller chunks. Try to track the size of the database

is DEBUG, in order to track searching for classes). If possible, please publish a database file that demonstrates the problem. support Support

you for this report and for the test case. The problem was added to the issue tracking

. You may browse the issue tracking system for more details. Missing JPA features are expected to be supported in

Just a quick thought. It would be nice to get email notification about new builds. If a new build resolves a problem that I'm not subscribed for, I don't know about it until i check ODB page :) lwalkowski Lukasz Walkowski This is a good idea. It is now set as a website feature request in the issue tracking system. support Support

    hello , is there any plan you have for monitoring objectdb realtime. Tracking queries and finding bottlenecks?   kadirbasol Kadir BASOL There is a ticket created by me. You can subscribe to it: https://www.objectdb.com/issue/169 and add you own requirements. lwalkowski Lukasz Walkowski

the database with the ObjectDB Doctor. But please do that in a separate thread in the issue tracking .  

This report was moved to the online  issue tracking  system. support Support

supported. Discussion was moved to a new feature request in the issue tracking . support Support

by ObjectDB. They are listed in the issue tracking system , and unfortunately subqueries

Sandeep Dhamale Inner queries are not supported yet. The issue tracking system contains

considerably more time from us, it could only be processed in the slower issue tracking route. Thank

a  feature request was add now to the issue tracking . The difference between these jars is that 

Software. So by browsing our issue tracking system , you can have a general idea of what will be included

Hello support, While tracking memory leak in my application i suspected a memory leak in the merging object db implementation. The test case is the following, just run and watch the "Memory Used" by comparing Cascade.ALL (or Cascade.MERGE ) to nothing. Tested with last version of Object Db ( 

to track all the old changes in these versions, but the exception of 2.4.5 is clearly wrong. Probably

that become unreachable ( tracked by using weak references). When a process starts it tries to delete

  makeTransient action, difficulties in tracking changes if the entity is made persistent

Hello All, I am trying to develop an ICT-Issue- Tracking application. The front end is to be java (for desktop version) and python or php for the web version but i want to code queries in native java and reduce the use of regular sql patterns. Can my application use the objectdb.jar to write

: public class OuterBlock extends Block implements TrackableUserType { // contains _odb tracking code

of other users of this forum who may track this thread it would be better to close this thread now but not to remove it (at least yet). support Support

the cause, please track the object version. You can do that easily by adding a version field

doppelrittberger Markus Ritter Use  enhanced classes  to get instant change tracking of all fields. They are also faster. support Support

the forum, the issue tracking and the download page and see that ObjectDB is different. Since it first

and a few other features, as you can see in the issue tracking ). support Support That is exactly what I needed

an issue (a bug report in the Issue Tracking system)? CBE CBE Build 2.6.8_07 should fix this issue

and tracking changes You can post as many questions as you want, but please follow the posting instructions

supports JPA 2.0 (except several unimplemented features - see the issue tracking ). Hibernate supports

\db\coreSystemDb.odb' is closed by 11028@wzbhb101 hgzwicker Hans-Georg Zwicker Further discussion of this report is in the issue tracking . support Support

to discuss this - issue tracking is only for clear bugs and precisely described feature requests. support Support

having much joy replicating the exact circumstances which cause it. I'll send an update if I can track

.type.user.UserMember.runInverseQuery(UserMember.java:467) at com.objectdb.pc. track .EntityTracker

and follow the posting instructions . Issue tracking is not for general questions. I am moving this post to the forum. support Support

John Francis We have spent some time tracking this down. If we do not do static enhancing we do not

- thats fine by me. Just for reference what environment are you running in? (Just in case I can track

every entity object with inverse fields tracking which inverse fields have been loaded and references

it says illegal arguement if i select something and search but i am setting correct value. Please find attached the full project. jmankari Jeevan Reddy Mankari This is not an issue tracking for Hibernate but for ObjectDB. support Support

versions (2.4.7, 2.4.6). If it is a new problem, we may be able to track the change the causes it. support

was added to that documentation page . The issue tracking system enables listing all the unsupported JDO

request, so it should have been posted to the forum and not to the issue tracking system. Please read

ObjectDB version 2.5.5 (and above) supports Java 8 (JDK 1.8). Tracking changes to collections and maps using some new Java 8 methods is currently not fully supported. The main known issue is that orphan removal does not happen as a result of removing a reference to an object