Internal Website Search

101-150 of 200 results

Managing software release cycles.

Schema Evolution Schema Update As you can see most schema changes are either fully automatic or

2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object"

without database schema change, and save some space in memory. You can still use StringIdentity ... id; and that might fix the issue, save memory, and not require database schema change (automatically ... replaced with @Index . You should be able to read old data with no schema change, as actually 

Failed to validate XML

Exception { if (null != em) { em.close(); } } /** Create database schema from entities. */ @Test public ... : download all three schemas from page - http://www.oracle.com/webfolder/technetwork/jsc/xml/ns ... .persistence" place into package all three downloaded schemas   Now project will work without any problem

Deadlock problems solved - a suggestion

the necessary schema changes (including creating the database if necessary), so that a database is already set up with the complete schema before an application runs?  All the information about the schema should be visible from a combination of XML files (such as package.jdo) and/or annotations

DB Explorer and Doctor unable to open DB file

synthetic classes from the schema . This synthetic class generation mechanism fails with your specific schema due to unknown reason. If you can share the relevant class files ( RackModel , 

ObjectDB embeddable Springboot

to examine the schema ?  tia lamininid Laminin if odb can be embedded like derby. Yes. ObjectDB ... is there a gui to examine the schema ?  Yes. The Explorer . support Support

@MappedSuperclass and @Transient not working as I expected

for classes annotated @MappedSuperclass also merely stored schemas , without the data? (I ... superclasses (as well as abstract entity classes) do not store data just schema . Usually data in

NPE when getting Persistence manager

There is some issue with the types in this database, possibly due to an old issue of unsupported schema ... and then with older version, so there might have been some schema upgrade in between, which the old

how explorer queries work

faking it somehow? jon jon ObjectDB stores the schema in the database (in the odb file) so it doesn't ... ObjectDB knows to build missing entity and embeddable classes, based on the schema that is internally

Removing an entity throws exception

images (used mainly to detected changes when enhancement is not in use) - after schema evolution. Therefore, starting with a new database file could solve the problem even with no fix, since the schema

InternalException & UserException using objectdb with Jboss AS 7.1.1 final

with a new empty database or after applying schema change. If you get this exceptions only with a new

Error using query with MAX() function

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

IDs of Entities suddenly became UUIDs?

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

InternalError on query of empty database

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

Explorer in 2.3

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

Update Entity references if we change the type of an entity

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

Join query problem with new statetment

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

General Performance Issues Illustrated with a Specific Method

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

virtual servers and one file

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

Composite Index error 328

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

newbie - lots of exeptions

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

ObjectDB version 2.1 has been released

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

Database size is much larger than expected (x2)

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

Indexing a field results in internal Exception

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

failure to enforce NOT NULL for java.lang.String

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

ObjectDB 2.8.7

to slow backup in client-server mode (see  feature request #2681 ). Fixed Explorer issue after schema evolution ( issue #2726 ). Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ).

'DROP TABLE' in ODB?

of this type in database I want to remove this type from schema . How can I do this? Is there something like ... kind of compiled classes into the schema ? But under the "File" Menu none such option is provided ... of deleting classes in the Explorer. An obsolete class can be selected in the Schema / Managed

Can't open replicated database

stack trace indicates an attempt to update a type schema in the replicated database, which is read ... is being used and not touch the schema ? I guess I can catch the exception and skip the query as I'll know

ObjectDB 2.2.3

Added support of @ElementCollection  (for setting eager fetch of non entity collections, such as List ). Improved performance of eager fetch in queries. Added Maven build enhancement to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema

Unexpected exception when execute query without enhanced entities

-enhanced class is not even used, as queries are compiled against the existing schema in the database ... a result of partial enhancement or maybe a recent schema change. support Support Actually I

ObjectDB 2.8.6_08

Fixed field renaming schema upgrade of previous schema versions ( issue #2713 ).

InternalException

schema changed require restarting the database. support Support Ah, that may be it. I did add a new ... must be restarted after a schema change , so this issue will be closed now. support Support

ObjectDB 2.6.4

on EntityManagerFactory close. Fixed a bug in hierarchy schema upgrade. Fixed a bug in schema upgrade that includes both class and field renaming.

Internal objectdb exception when using different language on a machine

. support Support Hello, we have to two databases. The main database contains the schemas of all entities ... contains only a restricted schema , here we have the only one not enhanced entity 'TCVector' (is not

InternalException

more quasado Alexander Adam Have you changed the schema recently (e.g. added new persistent fields ... may be the result of changing schema without restarting the database. support Support

ObjectDB 2.0.0

through inverse (mapped by) fields. Fixed some bugs in automatic schema evolution. Fixed a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool.

com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: 2

class versions between the client and the server, i.e, the server was updated to use a new class schema , which the client is unaware to yet. The ObjectDB server must be restarted after a schema change

stress test -> com.objectdb.o.InternalException: null

is to separate building the schema (i.e. registration of all the managed types) from the load test, i.e ... , and there is no redeployment or schema modification happening. Tomee is started

InternalException - error reading field from "queue" database

whose schema is not stored in the database, i.e. there are broken references from entity object field values ... replication? Maybe this is related to the other reported problem of inability to update the schema in

ObjectDB 2.5.1

on Schema Update during Multithreading activity ( issue #1139 ). Fixed a bug in loading mapped (inverse

NullPointerException in __odbGetNumMember

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

combined index not used

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

ObjectDB 2.6.8

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

ObjectDB 2.8.9_07

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 

Enum fields are set to null and embeddable enum class does not show in explorer

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

ArrayIndexOutOfBoundException

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

Allow removal of entity class from ObjectDB & Explorer

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

Error reading UTF string (Serialized Objects in Explorer)

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

queries under 2.7.6_4 significantly slower than under 2.7.6

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

NPE at com.objectdb.jpa.JpaQuery.getResultList

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