About named

151-160 of 200Refresh
Issue
19

Weird issue with variable naming

hi, We've hit again against troubles with the variable naming when trying to get the query string ... and order by. Removing the addition of order stuff solves the issue of double naming though doesn't help us without ordering. The issue is that the name of the root variable is $1 as well as the name
Forum
19

Duplicate Entity class names causes Exception in Query

I have two Entities which have the same class name but reside in different packages, only one of them is mentioned in the persistence.xml. I a NamedQuery I use the unqualified class name ... .... @Entity @NamedQueries({ @NamedQuery(name = "objdbTest.Singleton.getItem", query = "SELECT o
Manual
19

JPA Persistable Types

, package or private) and it can be either concrete or abstract. Entity Class Names Entity classes are represented in queries by entity names. By default, the entity name is the unqualified name of the entity class (i.e. the short class name excluding the package name). A different entity name can be set
Tutorial
19

Step 2: Entity Class and Persistence Unit

) and selecting New > Class. Enter guest as the package name - use exactly that case sensitive package name. Enter Guest as the class name - use exactly that case sensitive class name. Click Finish ... ; private String name; private Date signingDate; // Constructors: public Guest
Forum
18

Package name for persisted entities

Hi, I have a question about package name and searching for entities. As for now we were using ... . Unfortunately some of the names are the same for entities: - homplex.model.dbobject.Inspiration ... specify full name with package in persistence.xml and set "exclude-unlisted-classes" for true, ODB
Forum
18

Entity name

created a class named EBResult which looks like this: @Entity(name="RESULT") public class EBResult ... library) I expected to see an object named "RESULT" due to class annotation @Entity(name="RESULT"). Instead I see following: 2.1. Why? Is the @Entity(name="RESULT") ignored by ObjectDB? 2.2
Forum
18

Is named-query supported in orm.xml

I prefer to keep custom JPQL named queries in an external file, e.g. orm.xml, rather than in the entity classes, for example: <named-query name= "DataValue.deleteByCapabilityAndCreationtime ... and d.creationtime <= :creationtime named-query
JPA Doc
18

javax.persistence.metamodel.EntityType

Attribute getAttribute(String name) Return the attribute of the managed type that corresponds to the specified name. Return the attribute of the managed type that corresponds to the specified name. Parameters: name - the name of the represented attribute Returns: attribute with given name
Issue
18

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getWidthPxSideBarLeft ... . There is nothing wrong with the property name 'widthPxSideBarLeft', and I think this is a genuine ObjectDB problem ... Enhancer modifies the names of persistent property get and set methods by adding __odbHidden_ prefix
Forum
18

The attribute column name (EXCEPTION) is a reserved SQL-99 keyword.

How do I fix this error/warning that Netbeans gives me? "The attribute column name (EXCEPTION) is a reserved SQL-99 keyword." This warning indicates mapping to a field in the database that its name ... the name of the Java field to another name in the database: @Column(name="exceptionText") private