ObjectDB Database Search

101-150 of 200 results

ORDER BY problem, when String starts with language specific character

Dear all, I have a problem with ORDER BY clause. I have a simple query: select u from User u order by u.name When the name starts with "normal/english" character, records are ordered correctly ... anaq x ObjectDB uses the ordinal Java String lexicographical order , which is based on the order

Glassfish 3.1.2.1 and ObjectDB 2.4.3

- The requested resource () is not available. I tried it on Glassfish server 3 .1.2 and 3 .1.2.2. Sometimes I ... INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3 .1.2 (build 23) INFO: Grizzly ... ) at org.glassfish.hk2.classmodel.reflect.Parser$ 3 .call(Parser.java:307) at org.glassfish.hk2

How the sort order (in queries) works for non english letters?

(we are Czech company). How the sort order works for international (for us 'czech') letters? Does the ordering respects the national requirements? Thank you for clarification ... dmarko David Marko ObjectDB uses the ordinal Java String lexicographical order , which is based on the order

Closed EntityManagerFactory after upgrading glassfish 3.1.1 to 3.1.2

Hi. I have faced a very serious issue. After upgrading the GlassFish server from 3 .1.1 to 3 .1.2 ... more It seems that there is something wrong with persistent context. it seems that glassfish 3 .1.2 behaves differently. I tested another project which uses eclipseLink and java DB. it works well. glassfish 3 .1.1 logins

order by string with numbers

Hi Anyone could help me I need to order a string  for example user1, user2, ..., user1000 I ...   The sql that works is ORDER BY CAST(SUBSTR(username FROM 4) AS UNSIGNED) ASC Using JPQL SELECT u FROM Users u ORDER BY SUBSTRING(u.username,4)*1 ASC If you have other alternative for JPA

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

ObjectDB 2.7. 3 _03 gives my application a "com.objectdb.o.UserException: Attempt to modify ... ; (ObjectDB log file attached.) If I revert to ObjectDB 2.7. 3 , then no more exception.  (No other code ... . 3 _03 (which fixed an issue reported in this thread ). Could you please check version 2.7. 3 _04

Explorer in 2.3

servers, it may be faster for local files. 3 . On the Query page, please add a checkbox to request ... evaluation. For me, #1, #2 and # 3 would be the most important. Also, I've found some small bugs: 1 ... a very large array in the debugger). This will limit retrieval to open branches in the tree. 3

ObectDb 2.3.6 in OSGi environment

use a persistence.xml! The stacktrace looks like this: [ObjectDB 2. 3 .6] javax.persistence ... (BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$ 3 .run(ParentRunner.java:231) at org.junit ... ) at org.junit.runners.ParentRunner$ 3 .run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1

javax.transaction-api-1.3.jar and javax.persistence-api.2.2.jar

Hi, I notice that objectdb zip file has: javax.transaction-api-1. 3 .jar However that library ... this library at all? b) If I do need it, do I use jakarta.transaction-api 1. 3 or 2.0.1? Similarly java ... on version 3 .2 I'm guessing that in both cases I switch from javax to jakarta, but keep the same version as

GlassFish 3.1.2.2/JBoss 7.1.1

there are also issues with GlassFish 3 .1.2 (GlassFish 3 .1.1 may work better with ObjectDB ... 2.4. 3 can be used with JBoss AS 7.1.1. As discussed in this forum thread - you will have to: Add ... ;directory). Add to the persistence.xml file a request to load the ObjectDB module. Build 2.4. 3 fixes

2.5.3_02: java.lang.UnsupportedOperationException

Hello! I use Glassfish 4.0.0 and ObjectDB 2.5. 3 _02. When I do entityManager.createQuery I ... Glassfish 4.0 is based on JPA 2.1. Build 2.5. 3 _02 of ObjectDB added initial dummy implementation ... ; UnsupportedOperationException. Please try build 2.5. 3 _03, which adds now a real implementation

ObjectDB version 2.3 has been released

ObjectDB 2. 3 has been released and it includes important additions and fixes: Added the ability to edit databases in the Explorer ( issue #2 ). Added the ability to execute queries in the Explorer (issue # 3 ). Other small Explorer improvements. Added support of IN operator in JPQL queries. Added

NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1

When using inheritance throw exception java.lang.NoSuchFieldError: __odbTracker on NetBeans 7. 3 + Jboss 7.1.1 @Entity public class Person extends AbstractObject { private static final long ... ) if remove the inheritance works fine. On GlassFish 3 .1 with inheritance also works fine. Why "person

Issue with merge in 2.4.3

Hi, we just tried to upgrade to 2.4. 3 from 2.4.2. One of our regression tests is failing. Appears objects are getting created twice on merge. Please see attached unit test. Thanks Paul. pedwards Paul Edwards This regression bug was the result of a bad optimization  that is now fixed in build 2.4. 3 _01. support Support

Annotations not supported in -source1.3 (use -source 5 or higher ..)

and other files: Annotations not supported in -source1. 3 (use -source 5 or higher ..) Generics not supported in -source1. 3 (use -source 5 or higher ..) (Note that the version of Java I ran Maven as

Collation and String Order

will affect the way strings are sorted in queries (with ORDER BY). Currently strings are always ordered by Unicode order , and a workaround that enables controlling the order is to use normalizing, as ... feature. Many CRMs, DMS and other systems requires correct collation when using order by clause.  +1 for this ... dmarko David Marko

criteria api / embedded objects / where order

to the order of the where clouse and the 2.7.4 wasn't. Unfortunatly I was not able to strip ... to the order of the where clause, meaning that the result set differs. As far as I understand there might be some performence issues related to the order but no different result set

ObjectDB 2.3.3

ObjectDB 2.3.3

jakarta.persistence.Graph

to EntityGraph and Subgraph . See Also: EntityGraph Subgraph Since: Jakarta Persistence (JPA) 3 .2 Public ... is not an attribute of this entity.. Since: Jakarta Persistence (JPA) 3 .2 AttributeNode ... Persistence (JPA) 3 .2 void addAttributeNodes ( String... attributeName ) Add one or more attribute

jakarta.persistence.criteria.CriteriaQuery.orderBy(List)

orderBy (    List o ) Specify the ordering expressions that are used to order the query results. Replaces the previous ordering expressions, if any. If no ordering expressions are specified, the previous ordering , if any, is simply removed, and results will be returned in no particular order

jakarta.persistence.EntityGraph

.. Since: Jakarta Persistence (JPA) 3 .2 AttributeNode addAttributeNode ( Attribute attribute ) Get an existing ... : IllegalStateException - if the EntityGraph has been statically defined. Since: Jakarta Persistence (JPA) 3 .2 void ... . Since: Jakarta Persistence (JPA) 3 .2 Subgraph addElementSubgraph ( String attributeName ) Add

jakarta.persistence.Subgraph

. IllegalArgumentException - if the attribute is not an attribute of this entity.. Since: Jakarta Persistence (JPA) 3 .2 ... has been statically defined. Since: Jakarta Persistence (JPA) 3 .2 void addAttributeNodes ( String ... Persistence (JPA) 3 .2 Subgraph addElementSubgraph ( String attributeName ) Add a node to the graph

Apache License, Version 2.0, January 2004

Works in Source or Object form. 3 . Grant of Patent License . Subject to the terms and conditions

ObjectDB License Agreement [ver. 2.0.4]

by this agreement. 3 . The free edition of the Software includes restrictions on the number of classes

JPA Metamodel Types

The Jakarta Persistence (JPA) Metamodel API defines a structured hierarchy of interfaces and enumerations to represent the persistent types within a domain model. Metamodel Types Hierarchy in Jakarta Persistence (JPA) 3 .2 Base type definitions The core abstractions of model types

JPA Extended API Reference Guide

Jakarta Persistence API (JPA) 3 .2 documentation, generated from the official JavaDoc and enriched with practical notes. It groups the API types into logical sections to help you locate core concepts, query facilities, metamodel details, configuration options, annotations, and exception information

JPA Core Types

and inheritance relationships. Jakarta Persistence (JPA) 3 .2 Core Types Bootstrapping and Configuration

CRUD Database Operations with JPA

is greater than or equal to 100 are deleted. All other Point objects are updated. Chapter 3

Entity Management Settings

. For more details, see the Updating Entities section in Chapter 3 .

JPA Persistence Unit

(PersistenceConfiguration) Starting with  JPA 3 .2 , it is no longer mandatory to use a  persistence.xml  

JPA Criteria FROM and JOIN

is structured as follows: Criteria Query From Components in Jakarta Persistence (JPA) 3 .2 

ObjectDB Website - Terms and Conditions of Use

are under other licenses. See the Credits and Attributions page. 3 . Disclaimer The materials on ObjectDB

jakarta.persistence.NamedStoredProcedureQuery

must be specified in the order in which they occur in the parameter list of the stored procedure ... . The order of the specification of these mappings must be the same as the order in which the result sets ... about all parameters of the stored procedure. Parameters must be specified in the order in which they occur in

combined index not used

.properties.doubleValue FROM Action a WHERE a.type = 0 and a.subType = 3 and a.state = 3 and a.endDate = ?1 ... . [Step 1d] Filter the results of step 1c retaining only results that satisfy: (a.state= 3 ). [Step 1e] Filter the results of step 1d retaining only results that satisfy: (a.subType= 3 ). [Step 1f] Filter

jakarta.persistence.ConstructorResult

annotation in the same order as that of the argument list of the constructor. Any entities returned as ... , " + "COUNT(o) as orderCount, " + "AVG(o.price) AS avgOrder " + "FROM Customer c, Orders o ... of the intended constructor, in order . Since: Jakarta Persistence (JPA) 1.0 Additional JDK methods inherited

InternalException using 2.3.7_12

. 3 .7_02. I had to upgrade to 2. 3 .7_12 to pickup the fix for wildcard search on index, and now get this. [ObjectDB 2. 3 .7_12] Unexpected exception (Error 990) Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_21 (on Linux 3 .0.0-16-generic). Please report this error on http://www.objectdb.com

[ObjectDB 2.4.3_07] Unexpected exception (Error 990)

[2012-10-05 13:14:18 #7 store] Database '/home/glassfish/objectdb-2.4. 3 _07/db/test.odb' is opened by 7042@edi-gui-sbr-devel [2012-10-05 13:14:18 #8 server] [ObjectDB 2.4. 3 _07] Unexpected exception ... ] Database '/home/glassfish/objectdb-2.4. 3 _07/db/test.odb' is closed by 7042@edi-gui-sbr-devel hadnosoul

ClassCastException after upgrade to 2.3.5_03

" field is a byte[]. This worked ok in 2. 3 . 3 _06. felixobjectdb Richard Szurgot Thank you for this report. Please try build 2. 3 .5_04 that should fix this new issue. support Support

[ObjectDB 2.3.7_25] Unexpected exception (Error 990)

copy... [ObjectDB 2. 3 .7_25] Unexpected exception (Error 990)   Generated by Java HotSpot(TM) 64 ... :163) at com.objectdb.Doctor.main(Doctor.java:22) [ObjectDB 2. 3 .7_25] null lorenz2304 Benjamin Lorenz ... databases, but still if the database was created by an old version of ObjectDB (before 2. 3 .0) maybe

[ObjectDB 2.8.3_01] Unexpected exception (Error 990)

Seeing strange new error, with previously working code! Objectdb: 2.8. 3 _01 JVM: 1.8.0_252 OS: Ubuntu: 18.0.4 ----   [ObjectDB 2.8. 3 _01] Unexpected exception (Error 990) Generated by OpenJDK 64 ... .run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) [ObjectDB 2.8. 3 _01

Dynamic Metadata (JDO 3.0)

JDO 3 introduces the ability to specify and query metadata of persistable types dynamically. ObjectDB 2 supports specifying metadata by: JPA XML Mapping Metadata JPA Annotations JDO XML Metadata (e.g. package.jdo) JDO Annotations All these methods are static, i.e. the metadata has to be provided

NetBeans/JPA Java EE Tutorial

and menus might look slightly different but the code would be the same). Note: ObjectDB 2. 3 .7_04 or later is required if Glassfish 3 .1.2 (or later) is used. The Tutorial Steps This tutorial consists of the following steps:

Eclipse/JPA Spring MVC Web Tutorial

) including  Maven Integration for WTP (in m2eclipse extras). The tutorial was written for Eclipse 3

Getting Started with JPA and Eclipse

). This tutorial was written for Eclipse 3 .6.1 but it should work with other Eclipse versions as

Step 7: Run the Spring Web App

/. This Spring web application can also run with GlassFish 3 .0.1, with a small change in the 

Java EE JPA Tutorial - Maven Project

The  Java EE Web Application tutorial provides step by step instructions on how to build a simple Java/JPA database driven web application (for GlassFish 3 / JBoss 6) in  Eclipse or  NetBeans . Building a new application step by step is an effective way to learn - but 

Java EE Web Tutorial

This tutorial demonstrates how to create and run a full Java EE 6 MVC (Model View Controller) web application using GlassFish, ObjectDB and JPA. Since this web application uses Java EE 6 EJB (session beans) it requires a full Java EE 6 application server, such as GlassFish 3 .0.1 or JBoss AS 6

Eclipse/JPA Web Application Tutorial

(just download and extract). The tutorial was written for Eclipse 3 .6.1 but it should work

Step 1: Create a Java EE Web Project

We start by creating a new Java EE 6 Web Application project in NetBeans: Open the [New Project] dialog box, e.g. by using File New Project... Select Java Web Web Application and click Next . Choose a Project Name (e.g. Guestbook ) and click Next . Select GlassFish Server 3 (or above) 

Step 7: Run the Spring Web App

/Guestbook/. This tutorial should also run with GlassFish 3 .0.1, with a small change in