Internal Website Search

1-50 of 97 results

Auto Generated Values

strategies can be used as explained below. The Auto Strategy ObjectDB maintains a special global ... @GeneratedValue with the AUTO strategy: @Entity public class EntityWithAutoId1 { @Id @GeneratedValue ( strategy = GenerationType . AUTO ) long id; : } AUTO is the default strategy, so the following

Setting and Tuning of JPA Queries

: AUTO - changes are flushed before query execution and on commit/flush. COMMIT - changes are flushed only on explicit commit/flush. In most JPA implementations the default is AUTO . In ObjectDB ... time flush at the EntityManager level: em. setFlushMode ( FlushModeType . AUTO ); // Enable query time

javax.persistence.GenerationType.AUTO

JPA Enum Constant in javax.persistence.GenerationType AUTO Indicates that the persistence provider should pick an appropriate strategy for the particular database. The AUTO generation strategy may expect a database resource to exist, or it may attempt to create one. A vendor may provide

apache shardingsphere for auto sharding and replication possible ?

Hi , i have seen a project apache shardingsphere https://shardingsphere.apache.org/   You can look for detailed. It will be good if you add objectdb support for  Apache ShardingSphere   So we can use auto sharding and auto replication free...   kadirbasol Kadir BASOL

"Unsupported auto value type java.lang.String" when persisting new instance

I don't have a simple test case for this issue, but I'm getting this error: Exception in thread "main" [ObjectDB 2.3.2] javax.persistence.PersistenceException Unsupported auto value type java.lang ... .java:71) Caused by: com.objectdb.o.UserException: Unsupported auto value type java.lang.String

explorer feature request: ability to auto refresh

Request for feature: Ability to auto -refresh an explorer view, say at regular intervals of a few seconds. (at a minimum one ought to be able to manually refresh, for example the list of persistent types). additionally, it would be useful to be able to view an embedded database (read only mode

auto-generated uuid fields

Hello, we're porting a JDO application to ObjectDB which uses uuid-hex generated values. However the page on generated values in your JPA tutorial only mentions numeric generated values, and when we try to use it the error message seems to imply that auto -generating strings isn't supported

auto generate timestamp

Hi all, How can I create auto timestamping column? I want the database to generate the timestamp. I tried google but suggested solutions doesn't work in objectDB. http://stackoverflow.com/questions/811845/setting-a-jpa-timestamp-column-to-be-generated-by-the-database - Pawel   pawel Pawel

How to enable and disable auto schema update?

Hello, Can I enable and disable the auto schema update? In some cases if multiple applications are using same database and mistakenly one of application uses entity of older version build(my specified entity libs) then the whole db is being corrupted and db need to be restart.  Expected

Newbie : How to return the auto-generated ID

Hello, I am new to this community, as well as JPA and ObjectDB. I want to read the auto -generated ID when I persist a new entity (with @Id @GeneratedValue annotations applied). I am following the following link : http://www.objectdb.com/tutorial/jpa/eclipse/web/entity Thanks. zombie

Auto activiation of on-site licence for virtual VMs

In 2021 we asked about auto activiation of an on-site licence for adding and removing of virtual VMs. Has this feature been implemented? Kevin Kevin Pfaff It has not been implemented. However, you can run com.objectdb.Activator.main(null) from your application, redirect standard input to provide

ObjectDB auto sharding by simple algorithm

Hi , as i have seen objectdb doesnt have auto sharding feature. But its simple as below algorithm : ssedano/jump-consistent-hash: Java implementation of the jump consistent hash (github.com) Also checkout the documents i have given below: 1406.2294.pdf (arxiv.org)     I also added

javax.persistence.ValidationMode.AUTO

JPA Enum Constant in javax.persistence.ValidationMode AUTO If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider is present in the environment, no lifecycle event validation takes place. This is the default behavior. Since: JPA 2.0

javax.persistence.FlushModeType.AUTO

JPA Enum Constant in javax.persistence.FlushModeType AUTO (Default) Flushing to occur at query execution. Since: JPA 1.0

Auto Date for Creation and Update

Auto Date for Creation and Update

turn off auto-serialization

turn off auto-serialization

ODB should auto-restart if it detects it's necessary

ODB should auto-restart if it detects it's necessary

auto-generated uuid fields

auto-generated uuid fields

Entity Management Settings

for cascading persist operations: The always  attribute (whose value is "true" , "false" or " auto ... cascade settings. The " auto " value functions as "true" when using JDO and as "false" when using JPA

ObjectDB Object Database Features

.lang.BigDecimal. Auto Value Generation Modes (for primary Key fields) Database IDs - automatic

auto-generated uuid fields

Hello, we're porting a JDO application to ObjectDB which uses uuid-hex generated values. However the page on generated values in your JPA tutorial only mentions numeric generated values, and when we try to use it the error message seems to imply that auto -generating strings isn't supported

Feature suggestion: auto-detection of entities via persistence.xml extension

Feature suggestion: auto-detection of entities via persistence.xml extension

Spring Transactions (@Transactional) within ObjectDB

to  FlushModeType. AUTO . It is less efficient but it should guarantee that queries in ... how to FlushModeType. AUTO in ORM.xml we are not doing any annotations over our entity. Thanks in advance ... the EntityManager :     em.setFlushMode(FlushModeType. AUTO ); support Support I think I

Visibility of changes in Transaction is not visible to a JPA QL Query

most JPA implementations the default is AUTO . In ObjectDB the default is COMMIT (which is more efficient). support Support Yes, changing the Query to FlushModeType. AUTO meant that the added items ... which only show the values for all entities if the Query is in AUTO mode? No. Changes during transaction are not

On ensuring ID available after persist

up to another element) I am using the following for the ID: @Id //@GeneratedValue(strategy = GenerationType. AUTO )// Explicit for EclipseLink + Oracle or MySQL @GeneratedValue//ObjectDB takes as AUTO public Long getId ... ://www.objectdb.com/java/jpa/entity/generated :     Unlike AUTO and IDENTITY

javax.persistence.FlushModeType

.FlushModeType Flush mode setting. When queries are executed within a transaction, if FlushModeType. AUTO ... for the persistence context is AUTO (the default) and a flush mode setting has not been specified for the Query or ... , the persistence provider must not flush to the database. Since: JPA 1.0 Enum Constants AUTO (Default

javax.persistence.GenerationType

.0 The Auto Generated Values article explains how to use GenerationType . Enum Constants AUTO ... . The AUTO generation strategy may expect a database resource to exist, or it may attempt to create

Populating entity id before transaction commit

Hi, I have a question about populating auto generated id before transaction commit. We are using ... you can force early auto ID setting by: Object id = emf. getPersistenceUnitUtil() . getIdentifier() ;   support Support We are using ' Auto ' strategy right now, so I have to change our strategy

Remove a modified entity cause an optimistic lock exception

the object. Flushing changes to the database (by running a query in FlushModeType. AUTO ?) Removing ... (FlushModeType. AUTO );         em.getTransaction().begin();     ... FlushModeType. AUTO is set to the wrong EntityManager , i.e. to the one that is used to persist

@SequenceGenerator and single id in whole database

private long id; As I understand default strategy is Auto , which causes global ID's per database, not ... when strategy is AUTO (default). Maybe this should be changed and AUTO should use a generator if specified. support Support

Update more than 10000 entities by an update query fails

.createEntityManager(); emOne.getTransaction().begin(); emOne.setFlushMode(FlushModeType. AUTO ... .createEntityManager(); emTwo.getTransaction().begin(); emTwo.setFlushMode(FlushModeType. AUTO ); { String query ... (FlushModeType. AUTO ); { assertTrue(emThree.find(MyModelElement.class, 10000).isVisible()); assertTrue(emThree

javax.persistence.GeneratedValue

.0 The Auto Generated Values article explains how to use GeneratedValue . Public Annotation ... persistence provider. Since: JPA 1.0 GenerationType strategy default AUTO (Optional) The primary key

javax.persistence.Convert

) boolean fullTime; ... } Example 2: Auto -apply conversion of a basic attribute @Converter(autoApply=true ... disableConversion default false Used to disable an auto -apply or inherited converter

Duplicate Entity class names causes Exception in Query

.createNamedQuery("objdbTest.Singleton.count", Long.class); q.setFlushMode(FlushModeType. AUTO ); try { return ... demands we flush transaction to db if we wish to see its results   q.setFlushMode(FlushModeType. AUTO

Double persist of Entity field with Cascade.ALL

follows: @Id @GeneratedValue(strategy = GenerationType. AUTO ) private Long id; private String ... fields are as follows: @Id @GeneratedValue(strategy = GenerationType. AUTO ) private Long id; private

Join query problem with new statetment

= GenerationType. AUTO )     @Id     private long id;   ... , Convertable {     @GeneratedValue(strategy = GenerationType. AUTO )     

Beginners questions

") @GeneratedValue(strategy = GenerationType. AUTO ) private Long id; @OneToMany (fetch=FetchType.LAZY,cascade ... ; @Id @Column(name = "ID") @GeneratedValue(strategy = GenerationType. AUTO ) private Long id

[ODB1] Chapter 9 - ObjectDB Explorer

there are two assistant tab windows. The first tab window implements auto completion support for query definition. You can select elements from the auto completion list when you write the query filter

javax.persistence.TableGenerator

, generator="addressGen") int id; ... } See Also: GeneratedValue Since: JPA 1.0 The Auto Generated Values

javax.persistence.SequenceGenerator

) Since: JPA 1.0 The Auto Generated Values article explains how to use SequenceGenerator . Public Annotation

javax.persistence.ValidationMode

JPA Enum ValidationMode java.lang.Object ∟  java.lang.Enum ∟  javax.persistence.ValidationMode The validation mode to be used by the provider for the persistence unit. Since: JPA 2.0 Enum Constants AUTO If a Bean Validation provider is present in the environment, the persistence provider

javax.persistence.Converter

to override or disable auto -apply conversion on a per-attribute basis. If autoApply is false

javax.persistence.Convert.disableConversion

JPA Annotation Attribute in javax.persistence.Convert boolean disableConversion default false Used to disable an auto -apply or inherited converter. If disableConversion is true, the converter element should not be specified. Since: JPA 2.1

javax.persistence.GeneratedValue.strategy

JPA Annotation Attribute in javax.persistence.GeneratedValue GenerationType strategy default AUTO (Optional) The primary key generation strategy that the persistence provider must use to generate the annotated entity primary key. Since: JPA 1.0

[ODB1] Chapter 8 - ObjectDB Server

configuration is loaded automatically without having to restart the server. To turn off auto reloading

[ODB1] Chapter 3 - Persistent Classes

directories using the -s option (the "*.class" expression is in quote marks here to avoid auto resolving

[ODB1] Chapter 5 - JDO Connections

. This feature, which is called auto recovery , is not supported by the free edition of ObjectDB. To ensure

Explorer bug ? Objects seem to be missing from database in Class view, but are present as references

.Actor [29](TEST: Actor3) INFO: RequestBean []: Created: com.greensoft.entity.Actor [null](TEST: auto actor 0) INFO: RequestBean []: Persisted: com.greensoft.entity.Actor [30](TEST: auto actor 0) INFO: RequestBean []: Created: com.greensoft.entity.Actor [null](TEST: auto actor 1) INFO: RequestBean

new objects not available in mappedBy associations

is set to use FlushModeType. AUTO ). support Support What does this mean: "Try to refresh ... . I'll try to find a 'real' example, and I'll also examine the FlushModeType. AUTO option as suggested ... FlushModeType. AUTO in the EntityManager resulted in a huge exception message. dmoshal David Moshal Hmm, I

Tracking changes to new collections (in enhancement mode) after flush

.createEntityManager(); em.setFlushMode(FlushModeType. AUTO ); em.getTransaction().begin(); ModelElementImpl ... .createEntityManager(); em.setFlushMode(FlushModeType. AUTO ); em.getTransaction().begin ... (); em.setFlushMode(FlushModeType. AUTO ); em.getTransaction().begin