ObjectDB Database Search

(columnDefinition = "timestamp default '2020-04-10 20:47:05.967394'", updatable = false ) protected LocalDateTime createdDate; @CreatedBy @Column( updatable = false ) protected Integer createSicil ... .EAGER) @Column(name = "isEnabled", unique = false , nullable = false ) // @Column(columnDefinition

;           false          ... (readOnly = false ) public void addObject() {     Transfer transfer = new Transfer();   ... ()); } @Transactional(readOnly = false ) public void addObjectw() {     Transfer transfer = new Transfer

like the following fail to change the value from null to false : UPDATE RecordingMetaData AS r SET r.emergency= false WHERE r.emergency IS NULL DB Explorer reports all OK on the update, but a subsequent ... the same result: UPDATE RecordingMetaData AS r SET r.emergency= false WHERE r.emergency=null Updates

.management.jmxremote -Dcom.sun.management.jmxremote.port=16969 -Dcom.sun.management.jmxremote.ssl= false ... .jmxremote.port=16969 -Dcom.sun.management.jmxremote.ssl= false -Dcom.sun.management.jmxremote ... -Dcom.sun.management.jmxremote.port=16969 -Dcom.sun.management.jmxremote.ssl= false -Dcom.sun

: javax.jdo.option.Optimistic= false javax.jdo.option.NontransactionalRead=true javax.jdo.option.NontransactionalWrite= false javax.jdo.option.RetainValues=true javax.jdo.option.RestoreValues= false Now ... .jdo.option.RestoreValues= false The DB2 returns the message "Optimistic lock failed for object" or

; exclude-unlisted-classes to false rather than true . support Support After being pulled away from ... -classes to false . The Metamodel API still returns the empty set when 'getEntities()' is invoked ... configuration element back to false , and ran the original project.  The metadata was now accessible

();        // Both these turn out to be false !     assertTrue ... assertTrue(tmpDoc != null); // This turn out to be false ! assertTrue(readings != null); em.close(); emf ... = em.find(Document.class, doc.getId()); // This is false ! assertTrue(finalDoc.getReadings().size

;private transient boolean isEditable = false ; } @MappedSuperclass public abstract class BDOWA extends BDO ... = false 2. modificationTS = 2021-04-16 13:38:57 3. creationTS = 2021-04-16 13:38:03 4. tableId ... #33279 entry 1 has unexpected field count (7 instead of 5) 0. oid = '559770' 1. deleted = false 2

; @ManyToOne @Column(name = "VERLAG_ID") @JoinColumn(name="VERLAG_ID", insertable= false , updatable= false ... " which looks like this: public class Pojo { private transient boolean changed= false ; public boolean

my test cases are indicating that @Basic(optional= false ) and @Persistent(nullValue=NullValue ... (optional= false )         private String username;                 //@Basic(optional= false )  

where p.confirmed== false ", given me some results with p.confirmed==TRUE. And when I try to do (see image) "select p, p.confirmed  from Player p where p.confirmed== false ", I getting p-confirmed-true and p.confirmed- false . How so? And this problem not only in explorer mastervoland Vladimir Sadovnikov

private Date startTime; // Time: time part of startDateTime @Basic(optional = false ) @Temporal ... setStartDateTime(Date startDateTime) { this.startDateTime = startDateTime; } @Basic(optional = false ) @Temporal ... startDate) { this.startDate = startDate; } @Basic(optional = false ) @Temporal(TemporalType.TIME) public

instanceof ECompoundKeyMapItemId)) return false ; ECompoundKeyMapItemId other = (ECompoundKeyMapItemId ... )) return false ; ECompoundKeyMapSubItemId other = (ECompoundKeyMapSubItemId) o; return prnt.equals ... = System.currentTimeMillis(); container.generateMapItems(numItems, false , em); long beginCommit

_ID") @JoinColumn(name="VERLAG_ID", insertable= false , updatable= false ) private EBVerlag verlag=null; 3 ... this: public class Pojo { private transient boolean changed= false ; public boolean isChanged(){ return changed

an error if the query returns false . support Support Did something about this changed recently? In 2.9.0_02 it is returning false even when I added new activation key thamal Tomas Hamal No known changes here. support Support

' false , I got the same error that I reported at this new issue report (and for which I provided ... web app (too large to provide here) I however definitely have 'objectdb.temp.no-detach' false and I

ChildClassB(); entity3.onlyRecordLastStep = false ; em.persist(entity3); em.getTransaction().commit(); em ... public boolean onlyRecordLastStep = false ; protected ChildClassB() { } }   Then we rename SuperClass

) look like this org.hibernate.dialect.HSQLDialect thread 10 true false false create-drop I need

the case the id fields are not set if (!(object instanceof AbstractObject)) { return false ... != null && !this.id.equals(other.id))) { return false ; } return true; } @Override public String toString

backup" , Thread . class ) ; backupQuery . setParameter ( "start" , false ) ;      ... " ) ;     backupQuery . setParameter ( "start" , false ) ;      Thread

= false ) OR ($1.conditionThree= false )))) Exception in thread "main" [ObjectDB 2.2.8_04] Unexpected

= false ) private B b; @Id @Column(length = 36) private String stringId; } @MappedSuperclass public ... ); // false tsichevski Vladimir Tsichevski Point 2 is indeed a bug. Build 2.4.7_09 fixes

, password, false ); This will return the root directory, which then can be explored further using ... , false );   support Support Hi, thanks for your quick reply. It works great! skolb Sebastian Kolb

+ ... true and Boolean.TRUE are converted to 1. false and Boolean. FALSE are converted to 0. support Support

; // some integers describing photo characteristic Boolean isPublished; // either true or false ... the smallest subset of unique records (like for example "isPublished" which is either true or false

I am trying to understand the "embedded= false " for JDO byte[] as described in ObjectDB 1.0 Manual, sections 4.3 and 4.4.   I desire to store an image as a byte[] but I don't want the byte ... : @PersistenceCapable class MyImage{ boolean isCurrent; @Persist(embedded=" false ")byte[] imageData

.cLazy:{C}[2]"cLazy"
 b.cEager:{C}[3]"cEager" But when I switch DO_VIEW_BEFORE_CLOSE to false ... boolean DO_VIEW_BEFORE_CLOSE = false ;         /**    

, if we introduce the element and set it to false , we still get errors. I'm not sure, but I thinke we now ... ; index-update to false . Actually, such a stack trace is expected when  index-update is set

{     @Id @ManyToOne(cascade = CascadeType.ALL, optional = false )     ... .ALL, optional = false )     private Project project;        

; if (object == null ) return false ; if ( this .getClass() != object.getClass()) return false ; return

;set to false  or a new PersistenceManager for new operations (i.e.  PersistenceManager per request ). support Support Setting the PersistenceManagerFactory.retainValues to false works fine

, REVISION:=null, isPersisted:= false ... To confirm that the values are lost, I started the explorer ... markedDeleted = false ;   @ManyToOne   private Project project;   @javax.persistence.OneToMany

(); pm1.currentTransaction().setOptimistic( false ); pm1.currentTransaction().begin(); long numOfPictures ... .currentTransaction().setOptimistic( false ); pm2.currentTransaction().begin(); Picture picture2

= transaction.getEntity(id, false );             ... ;      Flight flight = transaction.getEntity(id, false );     

.currentTransaction()? 3) Does it lock at transaction.begin() if optimistic= false ?  4) Does it lock ... and therefore ObjectDB 1.0 Manual's statement suggests datastore transactions (optimistic= false ) would be faster

-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow-core-thread-timeout false INFO: SEC1002 ... thread-queue-capacity 2147483647 allow-core-thread-timeout false INFO: SEC1002: Security Manager

; @ManyToOne(optional = false , cascade = {})     @JoinColumn(name="PARENT_ID", nullable = false

]"b2"] When I set DO_VIEW_BEFORE_CLOSE false , so that the fields are only accessed ... = false . webel Dr Darren Kelly Actually there is no good reason for this. Build 2.3.7_05 removes

() == null ? true : false ; } catch (Exception e) { fileLocked = true;   If fileLocked is false

(java.lang.Object object) { if(this == object) return true; if(object == null) return false ; if(this.getClass() != object.getClass()) return false ; return Objects.equals(this.getUuid(), this.getClass

= "$objectdb/log/odb" max = "8mb" stdout = " false " stderr = " false " / path = "$objectdb/log/odb/archive ... " max = "8mb" stdout = " false " stderr = " false " /              

, nullable= false , updatable= false ) protected List projects = new ArrayList (); public List ... ; } @ManyToOne @JoinColumn(name="account_id", nullable= false ) public Account account; public Account

CBE You are right. This is a false alarm. The Doctor in 2.7.2 tries to diagnose index issues that have not been handled by previous versions but introduces this false alarm. Could you please try build 2.7.2_04? support Support ObjectDB 2.7.2_04 works as expected.  (No more false indexing issue

users use version-check=" false " and others version-check="true". This is probably not ... also a mixed environment in which some users use version-check=" false " and others version ... users use version-check=" false " and others version-check="true". hgzpincher Hans-Georg

Older objectdb-2.4.0_06, Java6. For the following (note the use of "is" form) in a class Element I encounter ObjectDB enhancement errors: private boolean loaded = false ; @Transient @Override ... . ... But it is ok using the 'get' getter form: private boolean loaded = false ; @Transient @Override public

findMomentPayloadEntities( false , maxResults, firstResult); } private List findMomentPayloadEntities ... ;    return findMomentPayloadEntities( false , maxResults, firstResult);    

. Using sync= false is faster but less safe (at least with some types of hardware), if objectdb is suddenly ... before starting to write to the database file. Although the default,  sync=" false

activation", boolean.class).getSingleResult()); Result is " false ". Also when trying to create ... .prepareDatabase(emf, "database"); Which results in the following output: false com.objectdb.o.UserException

I added a simple User entity during Tomcat startup: class User {  @Id @GeneratedValue private long id; @Basic(optional = false ) private String firstName; private String middleName; @Basic(optional = false ) private String lastName; } Everything works fine until I restart the server, which does

ChildClassB(); entity3.onlyRecordLastStep = false ; em.persist(entity3); em.getTransaction().commit(); em ... public boolean onlyRecordLastStep = false ; protected ChildClassB() { } }   Then we rename SuperClass