About false

1-10 of 200Refresh
Forum
41

@JoinColumn(nullable=false)

During the evaluation of ObjectDB (We're currently developing with EclipseLink/mysql) I noticed was the following: I marked a @Column as nullable=false Than I tried to save it with the property as ... (name="alarm_group_id", nullable=false) private AlarmGroup alarmGroup; ObjectDB silently ignores
Forum
41

Lock prevents PersistenceManager.close when retainValues = false

to false.  If retainValues == true, the code proceeds as expected.  I don't understand ... . The retainValues == false mode affects commit operations but should not affect close operation directly
Forum
40

recovery enabled="false", still creates tablename.odb$ files

Running in embedded mode, configuration specifies "".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb
Manual
39

Logical Operators in JPQL and Criteria API

must be one of: TRUE, FALSE, and NULL. The following table shows how the AND operator is evaluated based on its two operands:   TRUE FALSE NULL TRUE TRUE FALSE NULL FALSE FALSE FALSE FALSE NULL NULL FALSE NULL NULL represents unknown. Therefore, if one operand is NULL and the other operand is FALSE
Manual
33

Database Management Settings

enabled="true" sync="false" path="." max="128mb" />    element
Manual
29

Entity Management Settings

" />    false
Manual
21

Literals in JPQL and Criteria Queries

including NULL, boolean literals (TRUE and FALSE), numeric literals (e.g. 100), string literals (e.g ... two boolean literals - TRUE and FALSE. Since JPQL is case insensitive, TRUE is equivalent to true and True, and FALSE is equivalent to false and False. Numeric Literals JPQL supports the Java syntax as
Manual
17

Comparison in JPQL and Criteria API

== FALSE TRUE != TRUE FALSE Comparison operators are always evaluated to TRUE, FALSE or NULL. When both operands are not NULL (not shown in the table) the operator is evaluated to either TRUE or FALSE
Manual
17

Database Schema Evolution

with default values (0, false or null). Fields in the old schema that do not have matching fields in the new ... with a default value (0, false or null). The following type conversions are supported: From any numeric type ... and false are converted to false, any other value is converted to true). From any type to String (using
Manual
17

Collections in JPQL and Criteria Queries

IS EMPTY is TRUE if the collection is empty and FALSE otherwise. c.languages IS NOT EMPTY is FALSE ... .languages is TRUE if languages contains 'English' and FALSE if not. 'English' NOT MEMBER OF c.languages ...  parameter  is a collection that contains 'English' and FALSE if not. 'English' NOT IN :languages is TRUE