About dot

1-10 of 11Refresh
Manual
89

Paths and Types in JPQL and Criteria API

) and uses the dot (.) operator to navigate through persistent fields to other objects and values ... is a persistable user class can be extended further by reusing the dot (.) operator. For example, c ... class. The dot (.) operator cannot be applied to collections, maps and values of simple types
Result
24

ObjectDB Object Database Features

, AVG, MAX, MIN). Query Expressions Path navigation expressions using the dot (.) operator. Comparison
JPA Doc
12

javax.persistence.OrderBy

the ordering must correspond to columns for which comparison operators are supported. The dot ... used with the dot notation is the name of the respective embedded field or property. The OrderBy ... used. When specifying an ordering over an element collection of embeddable type, the dot notation
JPA Doc
10

javax.persistence.AssociationOverride

mappings at multiple levels of embedding, a dot (".") notation syntax must be used in the name element ... with the dot notation is the name of the respective embedded field or property. When AssociationOverride
JPA Doc
10

javax.persistence.AttributeOverride

map value. To override mappings at multiple levels of embedding, a dot (".") notation form ... identifier used with the dot notation is the name of the respective embedded field or property
JPA Doc
10

javax.persistence.ManyToMany

annotation to specify the relationship field or property of the embeddable class. The dot ... within the embedded attribute. The value of each identifier used with the dot notation is the name
JPA Doc
10

javax.persistence.ManyToOne

side of the relationship. The dot (".") notation syntax must be used in the mappedBy element ... with the dot notation is the name of the respective embedded field or property. Example 1
JPA Doc
10

javax.persistence.OneToOne

annotation to specify the relationship field or property of the embeddable class. The dot (".") notation ... within the embedded attribute. The value of each identifier used with the dot notation is the name of the respective
Issue
3

ODB Doctor Stops Progressing (runs forever)

Hi, I have an issue with the ODB Doctor running endlessly on a 1.35GB ODB file.  It gets to three progress dots quickly then stops progressing, all while consuming 100% CPU until killed manually ... progress dots before stopping.  It looks like it's hitting some sort of resource constraints, possibly
Issue
2

[ObjectDB 2.5.5_03] Unexpected exception (Error 990)

to get receiveTime1u6kopqt6zmjo from the not set parameter. I'll change my WHERE clause generator to remove dots