Internal Website Search
1-50 of 200 resultsServer User List The configuration element lists the users that are allowed to access the ObjectDB Server ... file contains the following element: The elements ... ... Every user is represented by a single element ... that have to be provided when the user connects to the server. The optional ip attribute, if specified, restricts | |
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 | |
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. ObjectDB supports all the JPA persistable types, which are: User defined classes - Entity classes ... types and Serializable types ( user or system defined). Note : Only instances of entity classes ... class is an ordinary user defined Java class whose instances can be stored in the database. The easy | |
Database Replication and Clustering above, a full URL has to be specified including user and password attributes. The slave server uses ... = Persistence.createEntityManagerFactory( "objectdb://localhost:6000/my.odb; user =a;password ... = Persistence.createEntityManagerFactory( "objectdb://localhost:6001//localhost:6000/my.odb; user =b | |
Database Connection using JPA = new HashMap (); properties.put("javax.persistence.jdbc. user ", "admin");   ... part of an ObjectDB connection URL: user - for specifying a username in client server mode. password - for specifying a user password in client server mode. drop - for deleting any existing database | |
Paths and Types in JPQL and Criteria API Instances of user defined persistable classes (entity classes, mapped super classes and embeddable ... are assigned as arguments. Path expressions that navigate from one object to another. Instances of user ... with an instance of a user defined class (represented by a variable, parameter or prefix path | |
JPA Metamodel API. getMetamodel (); The Metamodel interface provides several methods for exploring user defined persistable ... is an ancestor of interfaces that represent user defined types: EmbeddableType - represents user defined embeddable classes. IdentifiableType is as a super interface of: MappedSuperclassType | |
JPA Class Enhancer of compiled classes after compilation. Enhancement is mainly for user -defined persistable classes ... should be used (e.g. by using the get and set methods). If you follow this practice only user defined ... ; path to input user classes -pu : persistence unit name -s : include sub directories in | |
Locking in JPA update collisions resulting from simultaneous updates to the same data by two concurrent users . Locking ... if the version numbers do not match, indicating that the object has been modified by another user ... cannot be granted: A PESSIMISTIC_READ lock request fails if another user (which is represented by | |
SELECT clause (JPQL / Criteria API) objects (e.g. values of system types and user defined embeddable objects) return as results value ... several other methods for accessing the result data. CriteriaBuilder's construct JPQL user defined ... "))); The construct method builds a CompoundSelection instance, which represents results as instances of a user | |
Setting and Tuning of JPA Queries to anyone who uses em , even before committing the transaction (but not to users ... automatic optimistic locking to prevent concurrent changes to entity objects by multiple users . JPA 2 | |
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 that the name parameter is received as an input from the user and then embedded in the query string as is. Instead of a simple country name, a malicious user may provide JPQL expressions that change | |
ObjectDB Object Database Features API - any user with some experience with Hibernate, TopLink, EclipseLink, OpenJPA, JPOX or ... data structures very efficiently. User Defined Classes Entity classes (@Entity) Embeddable | |
JPA Persistence Unit A JPA Persistence Unit is a logical grouping of user defined persistable classes (entity classes, embeddable classes and mapped superclasses) with related settings. Defining a persistence unit ... registration of all the user defined persistable classes (entity classes, embeddable classes and mapped | |
General Settings and Logging specifying 0 as the maximum list size . The user attribute specifies if user names should be saved | |
Database Explorer of bookmarked entity objects. The [Schema] window shows the user defined persistable types (entity ... , however, do require setting the classpath. For instance, executing queries that include user defined | |
JPA Lifecycle Events Callback methods are user defined methods that are attached to entity lifecycle events and are invoked automatically by JPA when these events occur. Internal Callback Methods Internal callback methods are methods that are defined within an entity class. For example, the following entity class | |
Database Management Settings runtime is bundled in a product that uses only signed enhanced persistable classes - activation by end users is unnecessary. | |
JPA Entity Fields 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 (Mapped By) 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 | |
JPA Queries that is known only at runtime (e.g. depending on which fields are filled by a user in a form | |
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 and the changes are visible to other users (who use other EntityManager instances | |
Chapter 2 - JPA Entity Classes JPA Entity classes are user defined classes whose instances can be stored in a database. To store data in an ObjectDB database using JPA you have to define entity classes that represent your application data object model. This chapter explains how to define and use entity classes. | |
Eclipse Public License - v 1.0 may accept certain responsibilities with respect to end users , business partners and the like | |
Entity Management Settings of serializable types that are non persistable otherwise (e.g. a user defined class, which is not an entity | |
BIRT/ODA ObjectDB Driver://localhost/points.odb; user =admin;password=admin ). Click the Finish button to complete the creation | |
Comparison in JPQL and Criteria API). Enum values can be compared by using the equality operators (=, , == , != ). Instances of user | |
UPDATE SET Queries in JPA/JPQL transaction and the changes are visible to other users (who use other EntityManager instances | |
JPA Criteria API Queries;the criteria API may be preferred. For example, building a dynamic query based on fields that a user | |
Working with JPA Entity Objects Entity objects are in-memory instances of entity classes (persistable user defined classes), which can represent physical objects in the database. Managing an ObjectDB Object Database using JPA requires using entity objects for many operations, including storing, retrieving, updating and deleting | |
ObjectDB Overview a single file. Advanced querying and indexing capabilities. Effective in heavy loaded multi- user | |
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 JPA Query Language (JPQL) can be considered as an object oriented version of SQL. Users familiar with SQL should find JPQL very easy to learn and use. This chapter explains how to use JPQL as well as how to use the JPA Criteria API, which provides an alternative way for building queries in JPA | |
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 | |
[ODB1] Chapter 8 - ObjectDB Server, restart and start), and to exit the application. 8.2 Single User Server Configuration As ... 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 username and password | |
[ODB1] Chapter 7 - JDOQL Queries: Equality operators ( == , != ) compare the identity of instances of user persistent classes (as in Java ... expressions (a possible replacement to the like operator of SQL). To use methods of user defined classes in queries, the user code must be available. In embedded mode, user classes are always available | |
[ODB1] Chapter 5 - JDO Connections open for longer than necessary is not recommended in multi user applications because of the resources ... are usually required in a client server connection to enable user identification and permission ... - user desktop application using an embedded ObjectDB database (for example, a personal organizer). In | |
[ODB1] Chapter 6 - Persistent Objects of makePersistent( ... ) to instances of user defined persistent classes. However, persistence by ... , system types are embedded and user defined types (like the Address instance above) are not ... , while instances of user defined persistent classes are not (more details are provided in section 4.3 | |
[ODB1] Chapter 4 - JDO Metadata and references to user defined classes are excluded by default. The default-fetch-group attribute ... whose type is a user defined persistent classes or java.lang.Object . To use embedded objects for fields of user defined persistent classes, a metadata has to be specified as demonstrated by field f5 | |
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 whose instances | |
[ODB1] Chapter 9 - ObjectDB Explorer that the database contains (root objects are discussed in chapter 6 ). The "Query" window enables a user to execute ... , executing JDOQL queries containing user defined methods can be supported by the Explorer | |
[ODB1] Chapter 1 - About ObjectDB process, and multi user support may be achieved only by multithreading (several threads) in a single ... simultaneous requests using threads, even in embedded database mode, multi user access to a database |