ObjectDB Database Search
151-200 of 200 resultsrecovery enabled="false", still creates tablename.odb$ filesrecovery enabled="false", still creates tablename.odb$ files | |
DB Doctor with Recording enabled and using Database replicationDB Doctor with Recording enabled and using Database replication | |
select query for a HashMap field of an entity.select query for a HashMap field of an entity. | |
Class fields selection to storeClass fields selection to store | |
selective update does not workselective update does not work | |
Selective merge/cascade of detatched entitySelective merge/cascade of detatched entity | |
jakarta.persistence.criteria.Expression: - the type of the expression Super Interfaces: Selection , TupleElement Type for query expressions ... how to use Expression . Public Instance Methods Selection alias ( String name ) Assigns an alias to the selection item. Once assigned, an alias cannot be changed or reassigned. Returns the same selection | |
jakarta.persistence.criteria.CriteriaBuilder.SimpleCase.persistence.criteria.CriteriaBuilder.SimpleCase Super Interfaces: Expression , Selection , TupleElement ... which they are specified. Since: Jakarta Persistence (JPA) 1.0 Public Instance Methods Selection alias ( String name ) Assigns an alias to the selection item. Once assigned, an alias cannot be changed or | |
Enable intern() for Retrieved StringsEnable intern() for Retrieved Strings | |
jakarta.persistence.Cacheable: Annotation Target: Type Specifies whether an entity should be cached, if caching is enabled , and when the value of the persistence.xml caching element is SharedCacheMode. ENABLE _ SELECTIVE or SharedCacheMode.DISABLE_ SELECTIVE . The value of the Cacheable annotation is inherited by subclasses | |
JPA Query Expressions (JPQL / Criteria) JPQL and criteria queries are built on query expressions. Every query consists of clauses , such as SELECT , FROM , WHERE , GROUP BY , HAVING , and ORDER BY . Each clause is composed of JPQL or Criteria API expressions. Atomic expressions The atomic query expressions are: JPQL / Criteria Variables | |
Posting Sample Code(" SELECT e FROM MyEntity e"); List resultList = query | |
ObjectDB Object Database Features. Query Structure SELECT (including NEW ). FROM (including INNER JOIN , LEFT OUTER JOIN and JOIN | |
Chapter 4 - JPA Queries (JPQL / Criteria) clauses: SELECT , FROM , WHERE , GROUP BY , HAVING , and ORDER BY : The next section explains | |
JPA Primary Key might be necessary to evaluate the alternatives and select the best solution. | |
jakarta.persistence.TypedQuery: IllegalStateException - if called for a Jakarta Persistence query language SELECT statement or for a criteria ... to be a Jakarta Persistence query language SELECT query or a CriteriaQuery query. Since: Jakarta Persistence ... () Execute a SELECT query and return the query results as a typed List . Overrides Query.getResultList | |
jakarta.persistence.Query. Throws: IllegalStateException - if called for a Jakarta Persistence query language SELECT ... Persistence query language SELECT query or a CriteriaQuery query. Since: Jakarta Persistence (JPA) 2.0 ... () Execute a SELECT query and return the query results as an untyped List . Returns: a list of the results | |
jakarta.persistence.Convert to a basic type , enabling a converter defined autoApply=false , overriding the use of a converter ... instances contained in the map, or an entity class which extends a mapped superclass , to enable or | |
jakarta.persistence.EntityResult the SELECT clause of a SQL query to an entity result. If this annotation is used, the SQL statement should select all the columns that are mapped to the entity object. This should include foreign key ... . Example: Query q = em.createNativeQuery( " SELECT o.id, o.quantity, o.item, " + "i.id, i.name, i | |
jakarta.persistence.ColumnResult ConstructorResult annotation to map a column of the SELECT list of a SQL query. The name element references the name of a column in the SELECT list — i.e., column alias, if applicable. Scalar result types ... .createNativeQuery( " SELECT o.id AS order_id, " + "o.quantity AS order_quantity, " + "o.item AS | |
jakarta.persistence.EntityManager of TypedQuery for executing a Jakarta Persistence query language named query. The select list of the query ... if there is only one column in the select list.) Column values are returned in the order of their occurrence in the select list and default JDBC type mappings are applied. Parameters: sqlString | |
jakarta.persistence.criteria.AbstractQuery of query roots. Since: Jakarta Persistence (JPA) 1.0 Selection getSelection () Return the selection of the query, or null if no selection has been set. Returns: selection item. Since: Jakarta Persistence | |
jakarta.persistence.criteria.CriteriaQuery.multiselect(List) multiselect ( List selectionList ) Specify the selection items that are to be returned in the query result. Replaces the previously specified selection (s), if any. The type of the result ... method must not be a tuple- or array-valued compound selection item. The semantics of this method are as | |
jakarta.persistence.Converter only to attributes of the target type for which conversion is explicitly enabled via the Convert | |
jakarta.persistence.criteria.CriteriaBuilder.tuple(List) tuple ( List selections ) Create a tuple-valued selection item. Parameters: selections - list of selection items Returns: tuple-valued compound selection . Throws: IllegalArgumentException - if an argument is a tuple- or array-valued selection item. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.criteria.CriteriaBuilder.array(List) array ( List selections ) Create an array-valued selection item. Parameters: selections - list of selection items Returns: array-valued compound selection . Throws: IllegalArgumentException - if an argument is a tuple- or array-valued selection item. Since: Jakarta Persistence (JPA) 3.2 | |
jakarta.persistence.ConstructorResult to map the SELECT clause of a SQL query to a constructor. Applies a constructor for the target class ... is retrieved for the constructed object. Example: Query q = em.createNativeQuery( " SELECT c.id, c.name ... ColumnResult[] columns (Required) The mapping of columns in the SELECT list to the arguments | |
jakarta.persistence.FieldResult the SELECT list of a SQL query to the properties or fields of an entity class. Example: Query q = em.createNativeQuery( " SELECT o.id AS order_id, " + "o.quantity AS order_quantity, " + "o.item AS order_item ... column Name of the column in the SELECT clause - i.e., column aliases, if applicable. Since: Jakarta | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook HTML output: Open the [New JSP File] dialog box by right clicking the WEB-INF node under the Web Pages node (in the [Projects] window) and selecting New JSP ... Enter guest as the jsp file name - use exactly that case sensitive class | |
Step 4: Run the Application You can run the application now by right clicking the Main node (in the [Projects] window) and selecting Run File . The expected output in the [Output] window, is: Total Points: 1000 Average X: 499.5 (0,0) (1,1) (2,2) (3,3) : : (998,998) (999,999) When you run the application for the first time | |
Step 4: Add a Controller Class In this step we will add a Spring Controller to manage guestbook web requests: Open the [New Java Class] dialog box by right clicking the guest package node (in the [Package Explorer] window) and selecting New Class . The package name should be guest . Enter GuestController as | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Right click on the project in the [Package Explorer] window and select New Class . Enter tutorial as the package name (case sensitive). Enter Point as the class name (case sensitive). Click Finish to create | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the tutorial package node (in the [Projects] window) and selecting New Java Class ... Enter Point as the class name - use exactly that case sensitive | |
Step 6: Run the Java EE 6 Application You can run the application now by right clicking the GuestServlet node (in the [Project Explorer] window) and selecting Run As Run on Server Finish : Since we are using ObjectDB in embedded mode - the database file is created under the GlassFish directory (e.g. at domains\domain1\eclipseApps | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook page output: Open the [New JSP File] dialog box by right clicking the Web Pages node (in the [Projects] window) and selecting New JSP ... Enter guest as the jsp file name - use exactly that case sensitive class name. Click Finish | |
Step 4: Run the Application You can now run the application by right clicking the Main.java file (in the [ Package Explorer ] window) and selecting Run As Java Application . The expected output in the Eclipse [Console] window, is: Total Points: 1000 Average X: 499.5 (0,0) (1,1) (2,2) (3,3) : : (998,998) (999,999 | |
Step 6: Run the Web Application You can run the application now by right clicking the GuestServlet node (in the [Project Explorer] window) and selecting Run As Run on Server Finish : Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory. You can stop the Tomcat server and open | |
Step 3: Add a Main Class In this step we will add a main class to the project to store and retrieve Point objects from the database: Right click the tutorial package in the [Package Explorer] window and select New Class . The package name should be tutorial . Enter Main as the class name (case sensitive). Click Finish | |
Step 4: Add a Controller Class In this step we will add a Spring Controller to manage guestbook web requests: Open the [New Java Class] dialog box by right clicking the guest package node (in the [Projects] window) and selecting New Java Class ... Enter GuestController as the class name - use exactly that case sensitive class | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the project node (in the [Package Explorer] window) and selecting New Class . Enter guest as the package name - use exactly that case sensitive package | |
Step 6: Run the Java EE 6 Application You can run the application now by right clicking the GuestServlet node (in the [Projects] window), selecting Run File , and then clicking OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created | |
Step 6: Run the Web Application You can run the application now by right clicking the GuestServlet node (in the [Projects] window), selecting Run File , and then clicking OK (no need to change the servlet execution URI). Since we are using ObjectDB in embedded mode - the database file is created under the Tomcat directory | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook page output: Open the [New JSP File] dialog box by right clicking the Web Pages node (in the [Projects] window) and selecting New JSP ... Enter guest as the jsp file name - use exactly that case sensitive class name. Click Finish | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook page output: Open the [New JSP File] dialog box by right clicking the WebContent node (in the [Package Explorer] window), selecting New Other... Web JSP File and clicking Next . Enter guest as the jsp file name | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook HTML output: Open the [New JSP File] dialog box by right clicking WEB-INF under src/main/webapp (in the [Package Explorer] window), selecting New Other... Web JSP File and clicking Next . The parent folder should be WEB-INF | |
Step 4: Add a Servlet Class In this step we will add a servlet to manage guestbook web requests: Open the [New Servlet] dialog box by right clicking the guest package node (in the [Projects] window) and selecting New Servlet ... Enter GuestServlet as the class name - use exactly that case sensitive class name. The Java | |
Step 2: Define a JPA Entity Class To store objects in an ObjectDB database using JPA we need to define an entity class: Open the [New Java Class] dialog box, e.g. by right clicking the project node (in the [Projects] window) and selecting New Java Class ... Enter Guest as the class name - use exactly that case sensitive class name | |
Step 5: Add a JSP Page In this step we will add the JSP that generates the guestbook page output: Open the [New JSP File] dialog box by right clicking the WebContent node (in the [Package Explorer] window), selecting New Other... Web JSP File and clicking Next . Enter guest as the jsp file name - use exactly | |
Step 4: Add a Servlet Class In this step we will add a servlet to manage guestbook web requests: Open the [Create Servlet] dialog box by right clicking the guest package node (in the [Package Explorer] window), selecting New Other... Web Servlet and clicking Next . The Java package name should be guest. Enter | |
Which API should I use - JPA or JDO? that are supported only by JDO. Selecting the more popular API leads to more portable application |