Home » Search

About fix

101-110 of 200Refresh
Forum
1

ObjectDB's Database Doctor Incorrect Error Report

somehow this was not enforced by ObjectDB. This was fixed now so starting the next build ... . We preferred a soft fix rather than an exception in this immediate fix, and we will consider adding ... for the consideration and thank you more for the current fix and explainations.  =) BoydEdmondson
Forum
1

ODB IndexActivation NullPointerException

.6.7_07 includes an attempt to fix this exception. Please try it. Since we switch from ObjectDB 2.6 ... the additional picures of the thread states can help: Please try build 2.6.9_08 that should fix ... the version 2.6.1 and waited for a new version to fix. Unfortunatly the new version 2.7-1_01 does
Issue
1

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

possible and fix this carefully. I look forward to having this fixed and to having a robust ObjectDB ... _in_stateful Setting fetch=FetchType.EAGER on 'ownedElements' does seem to fix it (the lists load non ... and helping you fix bugs all week on my part, you owe my that much, even if it is to cure my delusion. I
Forum
1

Problem with distinct select, order by and equivalent alias/attribute path

. Do you have an idea for any workaround or could this be fixed? Is the last (problematic) query ... this fix/workaround in the test scenario, still trying to establish it in the "real" project. There I ... there to see if someone can fix it. For so long I will probably work around the issue by writing these queries by hand
Forum
1

Unable to convert 1.x odb file to 2.x

an attempt to fix them. Thanks for the fix. It helped for the above mistakes, but next one raised 200MB ... of objects as the value in the HashMap. Can this be fixed too?  This map issue would be much more difficult to fix, since no exception with a stack trace is available now. Therefore, we may need
Issue
1

Unexpected exception (Error 990) on find

. There was a problem with using large objects in the past, but it was fixed and we use tests ... it seems that you are experiencing a new problem. Apparently progress in fixing this would be possible only if we will be able ... to the report in issue #1977  that was fixed now in version 2.7.1. The new version fixes a critical bug that in
Forum
1

Wrong @Id type

UPDATE queries that was fixed. Please see this forum thread. Which ObjectDB version are you using? Try the last ObjectDB version, which should fix this issue/ To repair IDs that have already changed ... before the fix, with an UPDATE queries that change the IDs to the correct type). We are using ObjectDB
Forum
1

Possible cause for "Enhancement of type ... is old and cannot be used"

) You had attempted to fix it in build 2.6.6_08. I reported today on investigations by version here: http ... a TableGenerator. That problem was demonstrated by the provided test case, fixed in build 2.6.6_08 ... ).           The bug was found and fixed in build 2.6.9_01. It can affect any application that uses property
Issue
1

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

other errors (and to benefit from other fixes you have performed).     I appreciate that you usually prefer ... above, most ObjectDB users do not use property access so are not affected. Build 2.6.9_01 should fix ... and #3 are still relevant with 2.6.9_01 please let us know.   Thanks for the Build 2.6.9_01 fix
Result
1

ObjectDB version 2.0.1

Version 2.0.1 Fixed a bug in lazy loading of instances of non enhanced classes. Fixed a bug in using the Replayer with no updates to the database. Fixed an activation bug.