ObjectDB Database Search
1-50 of 200 resultsServer User List The configuration element lists the users who are allowed to access the ObjectDB Server ... contains the following element: The elements ... ... Each user is represented by a single element ... when the user connects to the server. The optional ip attribute, if specified, allows the user | |
jakarta.persistence.PersistenceConfiguration.JDBC_USER Jakarta Persistence (JPA) Field in jakarta.persistence.PersistenceConfiguration JDBC_ USER Username for JDBC authentication. Since: Jakarta Persistence (JPA) 1.0 | |
UserException - 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 | |
Acces the same DB with multiple usersAcces the same DB with multiple users | |
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 | |
Paths and Types in JPQL and Criteria API Instances of user -defined persistent classes (entity classes, mapped superclasses, and embeddable ... as arguments. Path expressions that navigate from one object to another. Instances of user -defined ... expression always starts with an instance of a user -defined class (represented by a variable | |
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 Metamodel API metamodel = em. getMetamodel (); The Metamodel interface provides several methods for exploring user ... for interfaces that represent user -defined types: EmbeddableType : Represents user -defined embeddable classes. IdentifiableType : The superinterface for: MappedSuperclassType : Represents user -defined mapped | |
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 | |
JPA Persistence Unit A JPA persistence unit is a logical grouping of user -defined persistable classes (entity classes ... ("jakarta.persistence.jdbc.url", "objectdb://localhost/my.odb") .property("jakarta.persistence.jdbc. user ... the database URL, user name, and password, as demonstrated above. XML mapping metadata ObjectDB supports | |
JPA Optimistic and Pessimistic Locking is essential to avoid update collisions when concurrent users simultaneously update the same data. In ... that another user (using another EntityManager ) has modified the object since the current transaction ... if the requested pessimistic lock cannot be granted: A PESSIMISTIC_READ lock request fails if another 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 | |
ObjectDB Object Database Features than other Object-Oriented Database Systems (ODBMS) - no need to learn a proprietary API - any user ... very efficiently. User Defined Classes Entity classes (@Entity) Embeddable types (@Embeddable | |
Database Explorer displays a list of bookmarked entities. The Schema window shows the user -defined persistable types ... , the Explorer can only execute queries that include user -defined methods if the code for those methods | |
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 Entity class is a user -defined class whose instances can be stored in a database. To store data in an ObjectDB database by 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 | |
Entity Management Settings method for instances of serializable types that are otherwise non-persistable (for example, a user | |
BIRT/ODA ObjectDB Driver (for example, objectdb://localhost/points.odb; user =admin;password=admin ). Click Finish to create the ObjectDB | |
Comparison in JPQL and Criteria API values: Can be compared using the equality operators ( = , , == , != ). User -defined class instances | |
Managing JPA Entities Entities are in-memory instances of entity classes (persistable, user -defined classes) that represent physical objects in the database. Managing an ObjectDB database with JPA requires using entities for many operations, including storing, retrieving, updating, and deleting database objects | |
General Settings and Logging the maximum size of this list. To disable this feature , set the size to 0 . The user attribute | |
ObjectDB Overview. Advanced querying and indexing capabilities. Effective in heavy loaded multi- user environments | |
ObjectDB Website - Terms and Conditions of Use of the site. Use of any such linked web site is at the user's own risk. 7. Site Terms of Use Modifications | |
Chapter 4 - JPA Queries (JPQL / Criteria) The Jakarta Persistence Query Language (JPQL) is an object-oriented version of SQL. Users familiar with SQL should find JPQL easy to learn and use. This chapter explains how to use JPQL and the Jakarta Persistence (JPA) Criteria Query API, which provides an alternative way to build queries in | |
SSL Configuration . createEntityManagerFactory ( "objectdbs://localhost/myDbFile.odb; user =admin;password=admin"); | |
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/nameFeature request: helpdesk user can change issue or support ticket page title/name | |
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 | |
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.SecondaryTable. Defaults to the default schema for user . Default: "" Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Table. Defaults to the default schema for user . Default: "" Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TableGenerator of the table. Defaults to the default schema for user . Default: "" Since: Jakarta Persistence (JPA) 1.0 String | |
Step 3: Create an ObjectDB Data Source-server (e.g. objectdb://localhost/points.odb; user =admin;password=admin ). You may click |