ObjectDB Database Search
1-50 of 200 resultsUserException - Object User#2 belongs to another EntityManager
Hi! Scenario's steps: 1. User goes to his profile, a JSF page. 2. @RequestScoped CDI bean UserDataB loads the current user of the session at each request, by using @Stateless bean UserC#findUserById(Long id) 3. JSF page's @RequestScoped CDI bean AnotherB loads trades of that user , by using
|
|
user defined backup target
Date/Time Information maybe: .. / Users /backup/mybackup.objectdb 2. What about the $odb File
|
|
Privacy Policy
visit and user actions during page views). Website refers to ObjectDB Website, accessible from ... information may include, but is not limited to: email address, username, full name, user name, profile ... gifs) that permit the Company, for example, to count users who have visited those pages or opened
|
|
JPA Persistable Types
supports all JPA persistable types, which include: User -defined classes: Entity classes, mapped ... types and serializable types ( user -defined or system-defined). Note : Only instances of entity classes ... is an ordinary user -defined Java class whose instances can be stored in the database. The easiest way
|
|
Database Replication and Clustering
the master database. As shown in the example, you must specify a full URL, including the user ... .createEntityManagerFactory( "objectdb://localhost:6000/my.odb; user =a;password=a"); Accessing the slave ... .createEntityManagerFactory( "objectdb://localhost:6001//localhost:6000/my.odb; user =b;password=b"); This URL specifies
|
|
JPA Connections and Transactions
.put("jakarta.persistence.jdbc. user ", "admin"); properties.put("jakarta.persistence.jdbc.password ... The following parameters are supported as part of an ObjectDB connection URL: user : Specifies a username in client-server mode. password : Specifies a user password in client-server mode. drop : Deletes
|
|
JPA Class Enhancer
the bytecode of compiled classes. Enhancement applies mainly to user -defined persistable classes ( entity ... (for example, the get and set methods). If you follow this practice, only user -defined persistable ... the CLASSPATH - path to class or jar file(s), *? wildcards supported include: -cp : path to input user
|
|
SELECT clause (JPQL / Criteria API)
and user -defined embeddable objects) return value copies that are not associated ... for accessing the result data. CriteriaBuilder.construct JPQL user -defined result objects ... , which represents results as instances of a user -defined class ( CountryAndCapital in the previous example
|
|
Setting and Tuning of JPA Queries
. However, these changes are not visible to users of other EntityManager instances. JPA implementations ... ) ObjectDB uses automatic optimistic locking to prevent concurrent changes to entities by multiple users
|
|
Is ObjectDB better than competing object databases?
, most object databases do not support user defined primary keys, even though this is very useful in almost every application. ObjectDB supports user defined primary keys including composite primary keys
|
|
Is ObjectDB scalable? What are its limitations?
ObjectDB is highly scalable and can manage efficiently databases in a wide range of sizes, from a few Kilobytes to hundreds of Gigabytes and even Terabytes. ObjectDB can be used in small embedded single user applications as well as in heavy loaded multi threaded multi user applications. ObjectDB
|
|
Query Parameters in JPA
the application to JPQL injection attacks. For example, suppose the name parameter is received as user input and then embedded in the query string as-is. A malicious user could provide JPQL expressions instead
|
|
JPA Lifecycle Events
Callback methods are user -defined methods that are attached to entity lifecycle events. JPA invokes these methods automatically when the corresponding events occur. Internal callback methods Internal callback methods are defined within an entity class. For example, the following entity class
|
|
Database Management Settings
. Therefore, when the ObjectDB runtime is bundled in a product that uses only signed, enhanced, persistable classes, activation by end users is unnecessary.
|
|
JPA Entity Fields
The fields of persistable user -defined classes (entity classes, embeddable classes, and mapped superclasses) can be classified into the following five groups: Transient fields Persistent fields Inverse ( mappedBy ) fields Primary key (ID) fields Version field The first three groups (transient
|
|
ObjectDB License Agreement [ver. 2.0.4]
that guarantees that any user of the Product and the embedded Software will be committed to the terms
|
|
ObjectDB License
a product to an unlimited number of end users . For a quote please contact ObjectDB Sales (sales
|
|
DELETE Queries in JPA/JPQL
within an active transaction. The changes become visible to other users (who use other EntityManager
|
|
Chapter 2 - JPA Entity Classes
An entity class is a user -defined class whose instances can be stored in a database. To store data in an ObjectDB database using Jakarta Persistence (JPA), you define entity classes that represent your application's data object model. This chapter contains the following sections:
|
|
Eclipse Public License - v 1.0
may accept certain responsibilities with respect to end users , business partners and the like
|
|
Negative snapshot user count
I finally hit an instance of the "Negative snapshot user count" exception 1) [ObjectDB 2.3.2_01 ... .InternalException: Negative snapshot user count com.objectdb.o.InternalException: Negative snapshot user count at com.objectdb.o.SNP.z(SNP.java:292) at com.objectdb.o.SFL.Z(SFL.java:765) at com.objectdb
|
|
user defined backup file
We need a way to do a (online) backup to a user defined backup-destination. Maybe in that way: backupQuery.setParameter("targetfile", new java.io.File("/ User /Backup/test.objectdb")); which should create a backupfile with the name ' test.objectdb " in the directory ' / User /Backup/ ' or backupQuery
|
|
Negative snapshot user count exception
.objectdb.com/database/issue/new com.objectdb.o.InternalException: Negative snapshot user count com.objectdb.o.InternalException: Negative snapshot user count at com.objectdb.o.SNP.D(SNP.java:344) at com ... , the "Negative snapshot user count" and the "mismatch client-server protocol" errors could be caused by
|
|
Feature request: helpdesk user can change issue or support ticket page title/name
Feature request: helpdesk user can change issue or support ticket page title/name
|
|
[ODB1] Chapter 8 - ObjectDB Server
to manage the server (stop, restart and start), and to exit the application. 8.2 Single User ... . This section discusses a simple configuration file with a single registered user . Notice that a single user configuration may also be used by multi user applications (such as web applications) where the same
|
|
Transaction isolation support?
of an object. To avoid using the same object by different users concurrently (even for read ... : We have a User class and a Book class, and each User have a list of books which the user ... the User table, just to make the explanation more easy). Now imagine the following where A and B
|
|
openejb jpa jaas module
.*; /** * Created with IntelliJ IDEA. * User : apple * Date: 31.01.2013 * Time: 06:01 * To change this template ... String username; private char[] password; private Map options; /** * User . */ protected String login ... (); properties.put("javax.persistence.jdbc. user ",options.get(" user ")); properties.put("javax.persistence.jdbc
|
|
Unable to convert 1.x odb file to 2.x
have been found: Type eu.extech.quant.data. user _attribute.UserAttributesMap, field "map" - 12 ... 10:58:29 #53 type.registry] New type eu.extech.quant.data. user _attribute.UserAttributesMap [2014-05-06 10:58:29 #54 type] Type eu.extech.quant.data. user _attribute.UserAttributesMap is not enhanced
|
|
jakarta.persistence.criteria.CriteriaQuery
from the query execution. If the type of the criteria query is CriteriaQuery for some user -defined ... the query execution. If the type of the criteria query is CriteriaQuery for some user -defined class X
|
|
Object explorer cannot open odb file. ObjectDB many-to-many relationship
in attachement) @Entity public class User { @Id private String code; @OneToMany(mappedBy = " user ") @MapKey private Map ... ; private User user ; @Id @ManyToOne(cascade = CascadeType
|
|
Handling deleted references
the following hierarchy: class User { Profile profile } class Profile { ... } Whenever the profile of a user is set to null we create a new (default) one to achieve that each user has a profile. To reset ... and no version. To simplify the use case I added a @PostLoad method to the User class, which simply checks
|
|
JSON serialization and __odbHidden members
before). Here's my class: public class User implements Serializable { private Long id; private ... ; private Profile profile; private List comments = new ArrayList (); public User (){ } // here the usual ... with relevant getters/setters) RESTful service class: @Path("/ user ") public class rs1
|
|
Trouble bug on explorer
numeric value of field field model. User .gid using enhanced method (error 362) at javax.swing ... .java:97) Caused by: com.objectdb.o.UserException: Failed to set numeric value of field field model. User ... more Caused by: java.lang.IllegalArgumentException at model. User .__odbSetNumMember(Unknown Source) at com
|
|
Level 2 cache not hit in @ManyToOne
Hi! I have 2 entities: User and Item, both @Cacheable. Item has @ManyToOne private User user ... " user ". " user " is loaded each time from the DB (tested by changing data in explorer and reading in my app). " user " should also be taken from L2 cache, shouldn't it? Otherwise...it's a huge
|
|
Optimistic Locking
an optimistic lock. I have two users logged on to our system. They both read and display the same data. Then I change the data with user 1 and submit, and then I change it with user 2 and submit. User 2 does not get an optimistic lock exception, so the database has user 2’s change
|
|
Type xxx is not found (error 301)
The error: Type User is not found (error 301) occurs when I query the db for a type before any instances of that type have been persisted, e.g.: return em.createQuery ("SELECT a FROM User ... query execution by using: em.find( User .class, User .class); but this is not
|
|
Dirty checking
view messages based on that graph of objects. e.g: if a collection of User Entity objects changed in a transaction, I'd like to generate a Json object with a list of the Users which were Added ... of thing. There are plenty of reactive user interface libraries, knockoutjs, Vuejs (actually based
|
|
objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation
] New type com.greensoft.objectdb.test.entity.value.BooleanValue [2016-08-24 16:14:34 #16 type. user ... .greensoft.objectdb.test.entity.value.EnumValue [2016-08-24 16:14:34 #19 type. user ] Enhancement ... #16 type. user ] Enhancement of type com.greensoft.objectdb.test.entity.value.BooleanValue is old
|
|
NPE after an @embedded obj is updated for a detached entity
I have an entity that looks like this: class User { @embedded private ... ; User user = entityManager.createQuery("select...... entityManager.detach( user ); user .getProfile().setDescription("Something... I get the following
|
|
jakarta.persistence.JoinTable
(Optional) The schema of the table. Defaults to the default schema for user . Default: "" Since: Jakarta
|
|
jakarta.persistence.Transient
: @Entity public class Employee { @Id int id; @Transient User currentUser; ... } Since: Jakarta
|
|
jakarta.persistence.CollectionTable
for the user is used. Default: "" Since: Jakarta Persistence (JPA) 1.0 JoinColumn[] joinColumns
|
|
jakarta.persistence.TableGenerator.schema
Jakarta Persistence (JPA) Method in jakarta.persistence.TableGenerator String schema (Optional) The schema of the table. Defaults to the default schema for user . Default: "" Since: Jakarta Persistence (JPA) 1.0
|
|
jakarta.persistence.Table.schema
Jakarta Persistence (JPA) Method in jakarta.persistence.Table String schema (Optional) The schema of the table. Defaults to the default schema for user . Default: "" Since: Jakarta Persistence (JPA) 1.0
|
|
[ODB1] Chapter 6 - Persistent Objects
( ... ) to instances of user defined persistent classes. However, persistence by reachability ... are embedded and user defined types (like the Address instance above) are not. This behavior ... .4 . Usually, instances of system persistent types are embedded by default, while instances of user
|
|
Step 3: Create an ObjectDB Data Source
-server (e.g. objectdb://localhost/points.odb; user =admin;password=admin ). You may click
|
|
[ODB1] Chapter 3 - Persistent Classes
Persistent Classes are user defined classes whose instances can be stored in a database using JDO ... for ArrayList ). Portable JDO applications, however, should only store instances of user defined persistent ... user classes -d output path for enhanced classes -s include sub directories in search -noopt disable
|
|
[ODB1] Chapter 2 - A Quick Tour
), is supported by ObjectDB but not by JDO. In JDO, only instances of special user defined classes ... of persistent classes. Persistent Classes Persistent classes are user defined classes
|
|
[ODB1] Chapter 9 - ObjectDB Explorer
that the database contains (root objects are discussed in chapter 6 ). The "Query" window enables a user ... . For instance, executing JDOQL queries containing user defined methods can be supported by the Explorer
|
|
2.9.x query issue with @Unique constraint
..) clause. It ignores the or operator. @Entity public class User { .. @Unique private String userName; .. } select u from User u where (u.userName = :userName or :userName is null) // null input ... User locating all the User (u) instances. [Step 2] Evaluate fields in User (u) instances. [Step 3
|