ObjectDB Database Search

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

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