160 | @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; bugsbunny2003 Marcel Rokers |
160 | Lock prevents PersistenceManager.close when retainValues = false to false. If retainValues == true, the code proceeds as expected. I don't understand ... for detachment during a PersistenceManager close operation. The retainValues == false mode affects commit |
159 | recovery enabled="false", still creates tablename.odb$ filesRunning in embedded mode, configuration specifies "<recovery enabled ="false"... />". 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 |
64 | 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 |
48 | 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 |
44 | 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 |
29 | Database Management Settings enabled="true" sync="false" path="." max="128mb" /> <recording enabled="false" sync="false" path ... " synchronized="false" /> <index-update enabled="true" priority="40" /> <query-cache results ... for most applications. The <recovery> element <recovery enabled="true" sync="false" path="." max |
26 | Entity Management Settings" /> <fetch hollow="true" /> <persist serialization="false" /> <cascade-persist always="auto" on-persist="false" on-commit="true" /> <dirty-tracking arrays="false" /> </entities ... specifies enhancement related settings: The agent attribute (whose value is "true" or "false |
2 | [ODB1] Chapter 5 - JDO Connections.option.Optimistic", "false"); properties.setProperty( "javax.jdo.option.NontransactionalRead", "true"); properties.setProperty( "javax.jdo.option.NontransactionalWrite", "false ... ( "javax.jdo.option.RestoreValues", "false"); PersistenceManagerFactory pmf = JDOHelper |
2 | [ODB1] Chapter 6 - Persistent Objects, false); The second argument of getObjectById(...) indicates whether or not the retrieved object ... = (Person)pm.getObjectById(oid, false); Notice that the newObjectIdInstance(...) method requires not ... [0]), s[1]); Person person = (Person)pm.getObjectById(oid, false); Retrieval by an Object Name |
