Internal Website Search

@Table(name = "PROJECT") @SequenceGenerator(name = "PROJECT_ SEQUENCE ", sequenceName = "PROJECT_ SEQUENCE ", allocationSize = 1, initialValue = 0) @SuppressWarnings({"PersistenceUnitPresent ... ; @GeneratedValue(strategy = GenerationType. SEQUENCE , generator = "PROJECT_ SEQUENCE ")    

(strategy = GenerationType.TABLE, generator = " sequences ") // @TableGenerator(name = " sequences ", initialValue = 1, allocationSize = 50) // @GeneratedValue(strategy = GenerationType. SEQUENCE

= GenerationType. SEQUENCE , generator = "sampleSeqGenerator") @Id long id;   The id field is as expected ... Mortimer Cladwell To obtain an automatic id on persist before commit use sequence or table strategy . support Support

to finding ID of entity before commit? lwalkowski Lukasz Walkowski You can use a SEQUENCE (or TABLE ... to sequence or table or I will try to force setting id. Thanks. lwalkowski Lukasz Walkowski

collation sequence . So I wonder if JPA will ever support this. Also, in an RDBMS, you can specify ... , since most international customers probably just use one collation sequence anyhow. Maybe some property

keys are sequential and therefore they are stored in sequence pages in the database. New objects ... objects their primary keys are sequential and therefore they are stored in sequence pages in

="RecordingMetaData_ sequence ", sequenceName="RecordingMetaData_ sequence ", allocationSize=1 ) @Indices

= "b", allocationSize = 1) public class Parent { @Id @GeneratedValue(strategy = GenerationType. SEQUENCE ... @GeneratedValue(strategy = GenerationType. SEQUENCE , generator = "b") private int id; @ManyToOne

- please consider: a different GeneratedValue 's strategy  (in ObjectDB the SEQUENCE  

=GenerationType. SEQUENCE , generator="user_pwd_seq")     @SequenceGenerator(name="user_pwd

@GeneratedValue (strategy = GenerationType. SEQUENCE , generator = "seq" ) private Long id

sequence executes when a track update comes in: - If it’s a new track simply add it to the database

=false   I can also confirm that the following sequence of updates works fine: UPDATE

; @GeneratedValue(strategy = GenerationType. SEQUENCE , generator = "gen") @Id private int principalId; public

less useful, unless  startDate is last. support Support the sequence of the index members is the key, thanks hgzwicker Hans-Georg Zwicker

This makes sense. The database file may have unused space, and if that space contains a long sequence

sequence of steps appear to be required (although I don't understand why): Stop client application (old

that you previously set manually. You may also try a different strategy. For example, if you use a sequence or

for the sequence of two builds, the last that works for you an the first that doesn't, and check

Hi, I have a question about @SequenceGenerator . I have separate @SequenceGenerator in each of my model enitities, but it looks like id's are generated using only one, shared generator. Is there any other way to use separate generators for each entity, so that each entity uses its own sequence

@GeneratedValue(strategy=GenerationType. SEQUENCE , generator="seq") private int gid; @Index private int id

to have the id available earlier (immediately after persist ) - you have to switch to sequence or table  value generation strategy. support Support

. SEQUENCE , generator = "asd") private int id; @Enumerated(EnumType.STRING) private ExampleEnum

We had a database failure causing a production outage. Both master and slave databases have failed, slave became unresponsive and the master switched to read-only mode. By the look of it the slave database failed first and possibly caused the master to switch to read-only mode. The sequence

.Thread.run(Thread.java:662) Is this expected behavior, due to AND not being sequenced , and an attempt

type. Fixed JDO sequence names to be fully qualified names (issue #1074 ). Fixed accessing a package level JDO sequence using getSequence ( issue #1074 ). Fixed false Doctor warnings when updating

(except that this may be related to using large number of entity classes and/or sequences ). Can you post a test that causes ... , and sequences is large. The workaround just increased the threshold but didn't fix the problem in the general

Support we are a bit lost, where do we find that list/ sequence of query plans ? hgzwicker Hans-Georg

The JPQL (Java Persistence Query Language) supports defining subqueries, which are nested queries that are embedded in other queries. Subqueries are currently not supported by ObjectDB, and as a workaround, you can use a sequence of two or more queries, where the results of one query serves as a parameter in the next queries. support Support

Zwicker one more sequence (system not more performing) hgzwicker Hans-Georg Zwicker we increased

graphs. Fixed a synchronization bug in sequence value generation. Fixed some issues in query execution

sequence that has caused the problem as until now this part of the process has been running fine

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

and can use individual sequence generator settings.       lwalkowski Lukasz Walkowski