ObjectDB Database Search

I have a class that is persisting a Entity that holds remarks and a time. Then when I query for the latest remark I get a internal error when the remark is larger than 1966 chars. Here is a test class and entity that reproduces the problem on my system. @Entity @Table(name = "TestEntity", schema

Maybe quasado can provide up to date information about this problem. Possibly there was a schema

the database about its current schema ? Thanks P. pedwards Paul Edwards Sure. Usually

tab is when I am interested in a specific piece of data that I will search for. The Schema tab

it seems that we cannot provide a quick implementation of this type of automatic schema evolution

execution. This might be caused by a schema change that is not fully supported. For example - changing

the Explorer schema tab). You should also run this query with logging enabled in the configuration

. Maybe depending on the creation date? It depends on your schema . Assuming you want to simulate random

Hi , when i try to use this entity as shown below: package persistence.jpa.models; import javax.jdo.annotations.Indices; import javax.persistence.*; import java.io.Serializable; import java.sql.Date; import java.util.Objects; @Entity @Table(name = "usrlist", schema = "posts") @NamedQueries

? Is it a primary key field? Are there recent schema changes in that class or class hierarchy

versions of the same entity are in use? If so, this could cause the schema to be repeatedly detected

with ordinary objects. Fixed a schema evolution bug when adding a new super entity class .   support Support

I store images into objectdb. The schema is : ::=( , , , , ) ::=String ::=char ::=int ::=byte[] ::=@ID So simple a class will fail after 155,648 insertions with -Xmx1432m, ... NO = 151552 @ 8042217472 id = 0 @ 7703244276 Url = http://cimg2.163.com/catchpic/E/E9/E96492634557CE291CDF3AADC710F373.jpg

after schema change. After adding an index to an existing entity class with instances in the database

a schema change is taking effect. running `mvn test` twice in a row without a clean between them does

the classpath, the Explorer uses the schema as defined in the odb file). Please try to remember

nothing whether such situations are allowed or forbidden. Unfortunately, in my schema the child id

a critical database corruption bug ( issue #187 ). Fixed a critical bug in schema evolution

Source) zmirc Mircea Chirac Currently schema changes require restarting the server

; Schema : artio; Owner: facman --   CREATE TYPE address AS ( street character varying, city character

.persistence.Lob; import javax.persistence.Table; @Entity @Table(name = "TestEntity", schema = "mySchema

When I use @OrderBy and supply multiple order fields I get and error when ObjectDB Explorer expands a instance of the entity. Example code: @Entity @Table(name="Defects", schema = "myDB") public class Defects implements Serializable {     ...     ...  

when searching and updating. 3. We run DB Doctor in recovery mode to generate a recovered DB file. No schema

are only required for a new entity type (e.g. analyzing and persisting the type schema , allocating

When I subclass a mappedSuperClass, a table for both appears in the Explorer. Am I correct to expect that only the subclass appear? If so, please provided any clues for a remedy. Thanks ... billdotnet Bill The super class is shown in the Explorer to enable viewing its schema and to enable opening

indexes should have no effect. Maybe you also changed a name of a field (without declaring the schema

, there is also a possibility that the data in the database is ok but something fails with the automatic schema

Hi: After a table built by real data, how to alter table structure, such as: alter table add column ... alter table add index ... TIA gzdillon Lai Yang There are no tables is ObjectDB. Anyway,  alter table add column ... This is automatic - just change your class (see Database Schema

a configuration file with many unused activation keys or having schema with hundreds of complex types

that it has to do with enhancement? quasado Alexander Adam It may also be related to schema evolution. Can you post the database

.no- schema -upgrade", "true"); EntityManagerFactory emf = Persistence.createEntityManagerFactory("D:\\odb

Added JPA XML validation schema files to Maven/JEE objectdb.jar. Added automatic release of pessimistic locks on client-server connection failure. Fixed an OptimisticLockException bug on commit after flushing a removed modified entity object. Fixed a  NullPointerExeption on new index building

Improved the error message on exception during commit, reported in issue #2882 . Improved automatic schema evolution of enum fields. Fixed A NullPointException when using EntityManagerFactory with different class loaders. Fixed a missing call to @PostUpdate when object change is detached by 

. It seems the enum class got lost in the schema . Could this be the case because the enum type has the same name as

classes are involved?  CacheableJobStat ? CacheableJobLog ? Could you describe their schema

the Schema / Managed Types list and then deleted by using [Edit Delete] from the menu bar or right click (context menu) and Delete. support Support

of this type in the explorer (by right clicking the type in the Schema tab and selecting Open Tree

) it may help identifying a pattern and finding a solution. If the schema and indexes are the same

; longpat Brian O'Hare Maybe the server was still running. Schema changes  requires server restart . I

of an old schema , in which the collection was not exist yet (as of changing attachment to attachments

reports.) CBE CBE In case it helps you (because 2.7.2_05 release notes state "Fixed a bug in schema

schema evolution of modified ancestor classes. Fixed a bug in handling indexes in a new ancestor

parameters display in the Explorer schema window. Fixed merging a new entity object with application set primary key.

of my entity look now like this: @Entity @Table( schema ="ebene1") public class MyEntity { protected static

Fixed unstable  activation issues. Fixed  issue #2954  - using IS NULL (or == null) on parameters in queries. Fixed automatic schema update on renaming or moving an enum type. Fixed issue #2964  (critical) - concurrent update of large objects with version-check=false.

( issue #1959 ). Fixed a schema evolution bug in handling hierarchy change . Fixed setting JDO's

Fixed Explorer issue after schema evolution ( issue #2726 ).

? Are there any recent schema changes to this database or any other changes specific to this application

Fixed automatic schema update on renaming or moving an enum type.

worked well before, it could be the result of a recent schema evolution. Particularly if you changed