ObjectDB Database Search

101-129 of 129 results


	@Lob @Basic(fetch = FetchType.LAZY) is loaded when it's not needed Vlad Myachikov FetchType.LAZY is a hint that JPA implementations are allowed to ignore. Currently
	Query performance in general the alternative is manual analysis of possible query plans and using hints to select a better query plan. support Support
	Dependency from enhanced classes to the objectDB library example? Then we may be able to solve the persistence unit not found exception using the hint at #2
	Performance tuning, best practices ? - should we change some settings in the configuration ? - other hints or proposals hgzwicker Hans-Georg
	Out of memory ;on the server side. Maybe changing some queries, setting indexes or using the objectdb.result-fetch hint
	Database Inconsistency or corruption someone already faced a similar problem ? Any hint is welcome ? junior
	Access entity version before commit transaction since it returns 3 here }); Hint : transactional.execute
	Is there any restriction when using fetch=FetchType.LAZY ? field (although it is only a hint in JPA and ObjectDB is allowed to ignore it and load data eagerly
	JPA and handling large data sets data sets the way is slow. We have an own entity for storing binary data (pictures, documents). Hint
	Unexpected internal exception during set field of an Embeddable to null that I found a important hint . The stack trace has been reduced to very (by the printer
	performance limit result loading, using the objectdb.result-fetch query's hint in order to separate query execution from
	Enhancement Check .objectdb.spi.SignedType support Support Hello, thank you for the hint , it performs. But we figured
	Occasionally slow requests in load testing a timeout for queries (using a hint ). support Support
	JBOSS AS7 7.1.1 - Entity not persisted and createNamedQuery fire exception ] (http--127.0.0.1-8080-1) persisted Guest count: 0 any hint on what's going on ? clicker
	Performance issue in a query due to internal calls visitRefs and visitKeyRefs Support thank you very much for the hint btc_es BTC EmbeddedSystems
	objectdb.java.util.ArrayList and performance this iteration. Can anybody give me a hint whats the reason or how i can increase performance here? ph
	ODB IndexActivation NullPointerException .objectdb.o.IXM.run(IXM.java:322) Maybe we have a not correct handled schema change or any other hint
	performance issues, database after adding statistics, after doctor search values. As a temporary workaround you can use a query hint to request using
	ObjectDB 2.8.4 ). Added support for a new query hint for setting a preferred variable processing order ( issue #2379 )
	Removed entities can be found by query in the same transaction a complex scenario. Maybe you have a hint how we can better analyze the issue or do you have an idea
	Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) (even though it is allowed by JPA - lazy is only a hint ), allocating IDs during persist
	InternalException when using MEMBER OF on a large list in a query they seem to be 36 bytes). support Support Thanks for the fix. Also thanks for the hint with long keys
	References to objects of missing obsolete entity classes not occur with objectDB version 2.8.0_4. Did you change anything and do you have any hint as
	Enable intern() for Retrieved Strings Implement a setting, where the developer can specify which Strings should be loaded via the String.intern() function. Hint for this enhancement: When loading a large list of persons, the persons first names are many time the same ones (here it is Martin, Michael, Thomas, ...). Instead
	Error during closing an entity manager Support I have a further hint . We have found a workaround for Issue #306 and this workaround prevents
	NullPointer when accessing entity field . Could you provide us some hint what is the cause of this problem? Thanks Marta Maruta M Sedlakova The cause
	NullPointerException: Cannot invoke "com.objectdb.o.RFV.S()" because "" is null Support Thanks for the hint with the query. I used the correct query in the code
	Unexpected Exception during commit I'm testing code that otherwise has been working with a clean database. I have seen several examples of the following exception. It never seems to happen in the same place twice, though. If you can give me a hint as to what would internally cause this, I'll try to reproduce it. Carl
	Lazy loading of mapped by (inverse) singular references ObjectDB ignores lazy setting of non collection mapped by (inverse) fields and loads them always eagerly. This is allowed by JPA since lazy is only hint but it is not efficient. The reason is that currently when an entity object is loaded all the referenced objects are instantiated