ObjectDB Database Search
1-50 of 96 resultsDatabase Schema Evolution in the new schema for which there is a matching field in the old schema, the new field in the new entity object is initialized using the value of the matching old field in the original entity object. Fields in the new schema that do not have matching fields in the old schema are initialized | |
Strings in JPQL and Criteria Queries. LIKE - String Pattern Matching with Wildcards The [NOT] LIKE operator checks if a specified string matches a specified pattern. The pattern may include ordinary characters as well as the following wildcard characters: The percent character ( % ) - which matches zero or more of any character | |
Recovery file does not match db file Just rebooted my production server, which had been running fine for months. When it came up, these errors started: ObjectDB 2.3.1_03] javax.persistence.PersistenceException Recovery file '/auctionologies/java/storage.odb$' does not match db file '/auctionologies/java/storage.odb' (error 145 | |
Object comparation never matches 2.4.6] javax.persistence.NoResultException" "No matching results for a unique query (error 782 | |
Documentation problem - license does not match implementationDocumentation problem - license does not match implementation | |
FROM clause (JPQL / Criteria API) outer variable value (e.g. any Country ) that has no matching inner variable (e.g. a Capital ... is equivalent to LEFT JOIN). When using OUTER JOIN, if a specific outer variable does not have any matching inner value it gets at least a NULL value as a matching value in the FROM iteration | |
Schema Update with persistable classes that have been renamed or moved in the IDE, with no matching schema configuration ... the application is run only with the configuration that matches these changes exactly. The default | |
JPA Lifecycle Events which is the source of the lifecycle event. The argument can have any type that matches the actual value | |
SELECT clause (JPQL / Criteria API) must have a compatible constructor that matches the SELECT result expressions, as follows: package example | |
Database Transaction Replayer ObjectDB can record its internal engine operations in special binary recording (journal) files. Recording is enabled by default and can be disabled in the configuration . The ObjectDB Replayer tool can apply recorded database operations on a matching database backup (if available). This ability | |
Index Definition a full index scan. Even better, if the field order as defined in the index matches the field order used in | |
SpringBoot-Point The architecture of this application follows regular SprintBoot principles, but minimized, to match | |
BIRT/ODA ObjectDB Driver and restarting the IDE. Note: See this issue regarding matching the driver version to the ObjectDB server | |
Paths and Types in JPQL and Criteria API class must contain a persistent field (or property) with a matching name. The path expression | |
Locking in JPA if the version numbers do not match , indicating that the object has been modified by another user | |
NoResultException: No matching results for a unique query I am very often getting a "com.objectdb.o._NoResultException: No matching results for a unique query" when modifying my already persisted entities within a transaction. I cannot replicate it however because it happens infrequently. The weird thing is that the entity nevertheless gets comitted | |
Query filter comparing Dates before saving: Tue Feb 02 01:00:00 CET 2021 Match found for filter : this.date == datum Date from DB instance : Tue Feb 02 00:00:00 CET 2021 Date from filter param : Tue Feb 02 01:00:00 CET 2021 Match ... 02 00:00:00 CET 2021 Date from filter param : Tue Feb 02 01:00:00 CET 2021 Match found for filter | |
Explorer in 2.3 the result (which, of course, must match the type of the field I am editing). Another possibility ... - copy any reference from any window and paste it on a field of a matching type. You can also edit ... it into a collection of a matching type (e.g. copy strings and then paste them into a List | |
Master database switching to read-only mode, possibly caused by slave failure are automatically routed to the slave, and the expected effect matches your description - READ requests ... manual intervention to get out of READ ONLY mode, so your description may match such situation ... to the master all the requests are automatically routed to the slave, and the expected effect matches | |
Step 1: Install BIRT and ObjectDB Driver matching the driver version to the ObjectDB server version when using client-server mode. The next step is creating a BIRT Report project . | |
Searching lists within objects how the database is doing its matching , but it looks to me like it matches using objectids, which means you can only match isMember if you have a database object. This does not help as I'm never going | |
Tomcat + JPA Problem always get this Error: [ObjectDB 2.1.0] class "javax.persistence.Entity"'s signer information does not match ... "'s signer information does not match signer information of other classes in the same package 07.03 ... .SecurityException: class "javax.persistence.Persistence"'s signer information does not match signer | |
Criteria Query results in a NoResultException instead of returning object.RuntimeException: com.objectdb.o._NoResultException: No matching results for a unique query at org.jboss.seam ... ._NoResultException: No matching results for a unique query at com.objectdb.o.JPE.g(JPE.java:100 ... ) ... 45 more Even though there exists an object that matches the query (check attached screen | |
Query to search for common elements in two separate collections. Support Sounds like you are suggesting a solution to matching the entire contents of a collection ... retrieving results for matches that contain the element for each iteration ... to matching the entire contents of a collection? Yes. if so, that's not what I was after. I just | |
AnnotationRef jakarta.persistence.IdClass , and the specified primary key type must have fields or properties with matching names and types. The mapping ... with names and types that match the Id fields and properties of the annotated entity class. Since: JPA 1.0 | |
Missing Data on Retrieval (0, null values) correctly but the Enity-Keys do not match . I can't get the point - what am i doing wrong? emf ... match between the two Resultlists Tested with Version 2.6.7 and 2.4.5 - same behaviour | |
LIKE wildcard with single character "_" behaves like a "*" Hi, I've been using pattern matching with wildcards, and encountered an issue when dealing with the underscore character. The issue is that if it is placed at the end of the string ... _") It matches both "key" and "keyboard" Having the underscore anywhere else works fine, however.  | |
virtual servers and one file you for the quick reply, I have checked all the links to VMware's knowledgebase for matches . None of them match . The virtual server is blazing fast on all other tasks as well, I rule out an I/O | |
ClassCastException on SELECT NEW ... after UPDATE over Java RMI rather than Long. Therefore, if the constructor of FileNameDTO expects a Long value there is no match ... soon. But meanwhile as a workaround, make sure that the type in the IN expression matches the type | |
Composite indexes a query that searches for exact match of several fields, any order would be fine. If you also need to get ordered results, then make sure that the requested order matches the index order. If you want | |
How to use regular expressions in Criteria Builder I'm struggling to understand how to use the matches method on the String class when using regular expressions. I have a small example with two classes. The TempPhysicalPartDetails class is embedded ... so you can use regular expressions in queries, just use string-based JPQL ("e.g. e.field. matches (regexp)") instead of criteria queries. support Support | |
JPA CriteriaQuery -- Iterate Expression | |
query hint must match one of the query plans logging text. Logging format and text might have changed between versions, so the string "index(ctso['(TC)'-'(TC)']" that worked in previous versions may match | |
Problems down-casting in WHERE clause)e).messageList.message. matches (:search) ((Practice)e).messageList.message is an invalid ... is valid: SELECT e FROM Practice e WHERE e.messageList.message. matches (:search | |
EnumRef jakarta.persistence.criteria.Predicate$BooleanOperator with the specified name. The string must match exactly an identifier used to declare an enum constant in | |
EnumRef jakarta.persistence.criteria.CriteriaBuilder$Trimspec constant of this type with the specified name. The string must match exactly an identifier used | |
EnumRef jakarta.persistence.metamodel.Bindable | |
EnumRef jakarta.persistence.metamodel.Attribute | |
AnnotationAttrRef jakarta.persistence.IdClass.value JPA Annotation Attribute in jakarta.persistence.IdClass Class value default null The primary key class, which must declare fields or properties with names and types that match the Id fields and properties of the annotated entity class. Since: JPA 1.0 | |
EnumRef jakarta.persistence.metamodel.Type | |
EnumRef jakarta.persistence.metamodel.PluralAttribute | |
query on calendar class is for literals, so it cannot contain variables or parameters. In comparison the operand types must match . Not | |
StackOverflowError after commit side), since it does not match the stack trace. In addition, this is only a partial stack trace. Please find | |
Mismatch client-server protocol prefix:757) I checked multiple times if the versions match . They do. DB server version 2.6.2. Client | |
General Performance Issues Illustrated with a Specific Method, which matches exactly post #1 on this thread. It seems that this log file has many query executions (21 | |
ObjectDB BIRT Driver Update, there should be a match between the ObjectDB BIRT client-server protocol version and an ObjectDB ... if there is no match . There is a report of an exception on attempt to update the ObjectDB BIRT plugin in | |
Logical "or" works not correcly when field is @Id and first position The following code doesn't respect the logical "or" correctly. Instead of returns all 2 datasets it returns only this one, which matches the first predicate in the or. BUT: this happens ... with the example code above, this query also returns only the object matches the b-tree (field | |
UPDATE statemen crash when i put the WHERE clause..createEntityManager() ; int lab_points ; for (List linie: linesAsList ) if (linie.get( 1 ). matches | |
Bug when using SIZE in combination with date lower parameter there are no matching jobs in the database? support Support Hello, yes, I can confirm that both queries | |
Eager load Map I'm having an issue eager loading a nested map. I've attached @ManyToMany(fetch=FetchType.EAGER) attributes to no avail. If the map is viewed in the debugger or force iterated in the code it loads ok. The attached code attempts to replicate the scenario. Its not an exact match but is the best I |