ObjectDB Database Search
51-100 of 200 resultsMaven driven compile time ehnancement classes during compile time . Just add the following to your pom.xml:   ... ; guest.Guest Actually, your phase is a better choice than mine, as mine only does compile time ... . support Support Ahh ok yes that makes sense. I've seen the issue many times in other systems | |
Compile time enhancement using build.xml of a Netbeans web application of a Netbeans web application project to specify ObjectDB compile time enhancement, for both single ... for Netbeans uploaded here would be very helpful. Until now I have been working with run- time enhancement ... enhancement and JRebel , as reported under: JRebel integration feature , so I want to try compile time | |
Query execution time issue about 10-12 seconds. If i remove ANY 5 left joins, query execution time drops to about 50 milliseconds. Adding a new left join on remaining 8 slows down query execution time drastically. Please help ... to, for exmple, 9 query execution time drops to about 60 milliseconds. Kind regards, Pero Pero | |
log entry date/time It would be very useful if each entry in the log file has a date/ time stamp. Thanks, Carl FastModel Ben Schreiber Version 2.2.2 adds date/ time stamps to the log. Thank you for your suggestion. support Support | |
EntityManager creation taking long time during the time of issue: From our logs the issue seems to have occurred between 3:45 am to 4:15 am on Nov 22nd ... such long wait times ? CAPdev CAP Dev There are no known issues that may be related. How do you know | |
EntityManager.refresh takes a long time EntityManager.refresh takes a long time for entity object Person in this code: logger.log(Level.INFO, "begin select for person " + new Date().toString());   ... only objects in his context? Operation time reaches 30 - 40 seconds. Please help to understand why.  | |
Option or strategy to disable/skip runtime enhancement checks (to improve load time)? Maven-based compile- time enhancement applied to entity modules (only), so I know these checks ... load time ) ? webel Dr Darren Kelly Please provide more information about these checks, such as log messages or stack traces. support Support | |
First persist takes long time We detected that the first Persist() of an entity take much longer than all subsequent calls. We have a small example (see Appendix) which outputs the following times : First transaction with persist ... : Could you explain the long time for first persist? btc_es BTC EmbeddedSystems Some operations | |
package.jdo validation error (Connection timed out) timed out: connect NestedThrowables: java.net.ConnectException: Connection timed out: connect The same | |
Post-compilation enhancement vs Automatic Run-time enhancement We are getting massively different results on field loading between explicit post-compile enhancement and automatic run- time enhancement. Testing exactly where and when the results are different for our demo web app is a very time consuming task, and very difficult, it means testing literally 100s | |
Retrieve latest entry in a time-series As mentioned elsewhere, subqueries are not currently supported. A subquery is the way that seems recommended to get only the latest entry in a time series (e.g. the latest time -clock entry for all employees). Is there an ObjectDB way to get the latest entry in a series?  | |
Issue with compile time enhancement I have an entity library which I have integrated build time enhancement in. The enhancer reports it has processed all of my persistent classes. When I attempt to run a Bootstrap process with this library I get the error shown below. The entity referenced in the error (Terms | |
Group by date / time support these expressions (as an extension to JPA) - support of date/ time methods ( YEAR , MONTH | |
java.time.* I get errors when trying to persist anything in java. time .* For example LocalDate, Month, Period. Will these be supported sometime in the future? scoobyrooster Jason Java 8 date and tome is not supported yet, except by serialization (which is not recommended and disabled by default | |
Open several objectdb databases the same time Golyshkin In embedded mode a database can only be accessed by one process at a time . The server mode | |
Java 8 time APIJava 8 time API | |
i can't change my password first timei can't change my password first time | |
several times a day queries take several minutes))) that normally take around 10 seconds but sometimes several times a day take around 3-10 minutes | |
queries more than 10 times slower using 2.8.1 versus 2.7.6 to avoid to again and again transfer this huge database, we are a bit under time pressure hgzwicker | |
jakarta.persistence.criteria.CriteriaBuilder to return current time . Returns: expression for current time . Since: Jakarta Persistence (JPA) 1.0 ... temporal ) Create an expression that returns the value of a field extracted from a date, time , or datetime. Parameters: field - a temporal field type temporal - a date, time , or datetime Returns | |
jakarta.persistence.EntityManagerFactory, there is exactly one EntityManagerFactory for each persistence unit: // create a factory at initialization time ... a new EntityManager instance each time it is invoked. The EntityManager.isOpen method will return ... specifying property settings. This method returns a new EntityManager instance each time it is invoked | |
jakarta.persistence.Basic , or Year Date or Calendar , java.sql.Date , java.sql. Time , or java.sql.Timestamp , byte[] or Byte ... getName() { return name; } The use of Date , Calendar , java.sql.Date , java.sql. Time , java.sql.Timestamp ... should use the date/ time types defined in the package java. time , or the primitive array types char | |
jakarta.persistence.TemporalType should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 The JPA ... Since: Jakarta Persistence (JPA) 1.0 TIME Map as java.sql. Time Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.LocalDateTimeField, numbered from 1. Since: Jakarta Persistence (JPA) 1.0 HOUR The hour of the day in 24-hour time ... a fractional part representing fractions of a second Since: Jakarta Persistence (JPA) 1.0 TIME The time | |
jakarta.persistence.Column of decimal digits to use for storing fractional seconds in a SQL time or timestamp column. Applies only to columns of time or timestamp type. The default value -1 indicates that fractional seconds should not be stored in a time column, or that the maximum number of digits supported by the database and JDBC | |
jakarta.persistence.MapKeyTemporal) protected Map employees; Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 2.0 Annotation Elements TemporalType value (Required | |
jakarta.persistence.EntityManager flush . The timing of the flush process depends on the flush mode , which may be set explicitly by ... time ). TransactionRequiredException - if there is no transaction when invoked on a container-managed | |
jakarta.persistence.Enumerated to be EnumType.ORDINAL . Example: public enum EmployeeStatus {FULL_ TIME , PART_ TIME , CONTRACT} public enum | |
jakarta.persistence.criteria.TemporalField Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.TemporalField Type Parameters: - the resulting type of the extracted value - the temporal type (date, time , or datetime) Each instance represents a type of field which can be extracted from a date, time , or datetime | |
jakarta.persistence.Temporal/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 The JPA Persistable Types | |
jakarta.persistence.Column.secondPrecision) The number of decimal digits to use for storing fractional seconds in a SQL time or timestamp column. Applies only to columns of time or timestamp type. The default value -1 indicates that fractional seconds should not be stored in a time column, or that the maximum number of digits supported by | |
jakarta.persistence.TypedQuery.setParameter(Parameter,Date,TemporalType) should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.setParameter(String,Calendar,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.setParameter(String,Date,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.setParameter(Parameter,Calendar,TemporalType) code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.setParameter(int,Calendar,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.TypedQuery.setParameter(int,Date,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(int,Calendar,TemporalType) the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(int,Date,TemporalType) if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(Parameter,Date,TemporalType): Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(String,Calendar,TemporalType)/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(String,Date,TemporalType) if the value argument is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.StoredProcedureQuery.setParameter(Parameter,Calendar,TemporalType). Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.setParameter(int,Date,TemporalType) type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.setParameter(String,Calendar,TemporalType) type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.setParameter(String,Date,TemporalType). Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.setParameter(int,Calendar,TemporalType) is of incorrect type. Deprecated: Newly-written code should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.CriteriaBuilder.currentTime() Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Expression currentTime() Create expression to return current time . Returns: expression for current time . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Query.setParameter(Parameter,Calendar,TemporalType) should use the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 2.0 | |
jakarta.persistence.Query.setParameter(Parameter,Date,TemporalType) the date/ time types defined in java. time . Since: Jakarta Persistence (JPA) 2.0 |