ObjectDB Database Search

JPA Static Field in jakarta.persistence.criteria.LocalDateTimeField YEAR The calendar year . Since: JPA 3.2

JPA Static Field in jakarta.persistence.criteria.LocalDateField YEAR The calendar year . Since: JPA 3.2

such functions as an extension. ObjectDB supports 6 functions for extracting the YEAR , MONTH , DAY , HOUR , MINUTE and SECOND . For example: YEAR ({d '2011-12-31'}) is evaluated to 2011 . MONTH({d ... method, as follow: // Create expressions that extract date parts:    Expression year = cb

to this Agreement will bring a legal action under this Agreement more than one year after the cause of action

profiling sessions). Unique data structures and algorithms (as a result of years of R&D). Outperforms

=3600000,endTimeMode=2]],firstDayOfWeek=2,minimalDaysInFirstWeek=4,ERA=1, YEAR =2011,MONTH=4,WEEK_OF_ YEAR =22,WEEK_OF_MONTH=5,DAY_OF_MONTH=30,DAY_OF_ YEAR =150,DAY_OF_WEEK=2,DAY_OF_WEEK_IN_MONTH=5,AM_PM=1,HOUR=7 ... ,minimalDaysInFirstWeek=4,ERA=1, YEAR =2011,MONTH=4,WEEK_OF_ YEAR =22,WEEK_OF_MONTH=5,DAY_OF_MONTH=30,DAY_OF_ YEAR =150

Hi, I'm trying to create reporting query that will return entities grouped by year / mont / day. Each entity has it's own field that holds java.lang.Date. There is no function like YEAR (), MONTH ... WHERE YEAR (record_date) = 2009 GROUP BY YEAR (record_date), MONTH(record_date) or maybe

years old and don't cover annotations.  Is JDO and object databases (and therefore ObjectDB ... than JDO's. JPA turned out to be the right choice for me. I have about 10 years of development experience with GemStone S, moderate experience playing with db4o, and now several years with Objectdb. I

, numbered from 0 to 59. Since: JPA 3.2 MONTH The calendar month of the year , numbered from 1 ... Since: JPA 3.2 TIME The plain part of a datetime. Since: JPA 3.2 WEEK The ISO-8601 week number. Since: JPA 3.2 YEAR The calendar year . Since: JPA 3.2

, numbered from 1. Since: JPA 3.2 MONTH The calendar month of the year , numbered from 1. Since: JPA 3.2 QUARTER The calendar quarter, numbered from 1 to 4. Since: JPA 3.2 WEEK The ISO-8601 week number. Since: JPA 3.2 YEAR The calendar year . Since: JPA 3.2

. It is really tiresome. As we bought the license years ago there was hinted at a automatic ... ;. However, we do not have control on the MAC address, and changes in recent years ... you are using an old 5- year version of ObjectDB. Newer versions (starting 2.9.3) are much better

.getDays()); if (getAgeYears() 12) { setAge(period.getYears() + " years ."); } else if (getAgeYears() 0) { setAge(period.getYears() + " years and " + period.getMonths() + " months."); } else { setAge ... and please note that I have been following these documents for about 7 years now. You do not try

Hi, For how long ObjectDB will exist and will be actively maintained? Will it still be there in 10 years ? In 20 years ? Thanks. randomguy Anton Yes, ObjectDB is an active project and will probably be here in the next 10, 20 and 50 years . Your question is fair because the ODBMS market in general

(from documentation): YEAR ({d '2011-12-31'}) is evaluated to 2011. MONTH({d '2011-12-31 ... have to group by date(). For few queries I was concatenating 'date' from year ()-month()-day() calls ...  in queries: DATE(ts) - Extracts the date part ( year , month, day) as a Date instance. TIME(ts

Hi I haven't used objectdb for 2 years and are considering to use it in a new project. Are there any news on objectdb 3.0, I have noticed there are no new releases for more than a year . Best regards peric.emil Emil Perić Actually there were several releases in the last year (including version 2.8

findAllByBirthDateYear ( int year );      @Query ( " Select p from Person p WHERE YEAR ( p . birthDate ) = : year " ) } In order to avoid the need to configure RDBMS in application

am perplexed as I have use JPA and ObjectDB for years now. I could use your assistance in ... that has already been fixed. The stack trace is produced by ObjectDB 2.3.7, which is 2 years old now, and many issues have been fixed in the last 2 years . Please try switching to the last ObjectDB version

;   } This code worked for a couple of years now and is used in multiple projects. mosi0815 ... this method for over 3 years now. It's from the early days of our software when we used MySQL

.' The JRebel technology is helping to save me months of development time per year , and it helps avoid ... , for the first time in years (I had tried JRebel many times before but the clashes with ObjectDB

on ObjectDB since the beginning of this year , but I think it would be much better if your db ... , and with relational and object DBMSs for over thirty years . I'm currently building foundation

the engine that manages the database storage, at least in the last 2 years , so there is nothing in version 2 ... for years , the hope was that switching to 2.8 solves these problems (that was an advise of objectdb

, and it has been like that for 1 year , since I started using ObjectDB. I'm also accessing from Europe, and many ... (and we tried several different providers, including Amazon, in the last year ) hasn't solved

.thondavada Saiprasad Thondavada It’s good to see that a 10- year -old version of ObjectDB ... by your application). However, any upgrade that spans several years may introduce subtle issues

. YEAR ), to.get(Calendar.MONTH), 1);         if (to.after(now ... ;     from.set(from.get(Calendar. YEAR ), from.get(Calendar.MONTH), 1);   

Hello I am using embedded objectdb in a 4  years old project. Over the years the data got bigger and now I want to make some performce improvements for some specific part of the code. Lets say we have a Parent and Child class with onetomany relation @Entity class Parent { @Id Long id

JPA Static Field in jakarta.persistence.criteria.LocalDateTimeField MONTH The calendar month of the year , numbered from 1. Since: JPA 3.2

.OffsetDateTime , java.time.Instant , or java.time. Year java.util.Date or java.util.Calendar , java.sql

JPA Static Field in jakarta.persistence.criteria.LocalDateField MONTH The calendar month of the year , numbered from 1. Since: JPA 3.2

assured, my prototype app (Stale as of july last year due to work commitments) has never seen the issue

Hi, We're having our system with ObjectDB 2.4.5 in production since this year April and it works just fine. However, now we've discovered that suddenly partial Objects in some DBs in production do have a UUID String as their id instead of Long which is of course causing a lot of troubles. Note

incremental backup later this year . support Support Great news. Does this plan also include

I'm considering using ObjectDB in a system that is going to be running continuously without support instantly available for many years .  How stable is ObjectDB when it comes to power failures and unattended restarts?  Is database integrity maintained during such events?  I have seen

; Calendar cal = Calendar.getInstance();         cal.set(Calendar. YEAR

;  calendar.set(Calendar. YEAR , 1970);         calendar.set

they are, since the update of that version was from last year .  How do I find out exact I'm running

After years of evaluation and development using objectdb, we are finally about to release a product.  There have been bugs to deal with, but we have stayed with objectdb because it is as fast as it promises, and the support when we have had problems has been first class.  Thanks

Steve Zara Development of JDO in the recent years is slow, and there are only a few JDO features

requests and currently costs £2,400/ year . support Support

You provided the "InsertTest" in the following post, and say "On Intel Core 2 Quad Q6600 (and enhancement) it persists 340,000 objects per second". Insertion Speed Rate and Batch Load Now, ten years later, I run it on Intel Core i5-5300U (2.3Ghz) with 8GB memory, output is 45000 per second

? support Support it does not happen with 2.7 (it was working for years ) 2.8.9 not checked

Ran into this error for the first time (after many years of using odb): Caused by: com.objectdb.o._OptimisticLockException: Optimistic lock failed for object model.UserSession#28 (object has version 2 instead of 3) Also the first time I'm using odb in C/S mode rather than embedded

would have thought that would be done automatically. Having used objectdb for nearly 10 years now, all in

time (I think 2 years ?) without these issues, two possible factors may be relevant: Your move from ... .3.x would be a problem because development work I did this year relies on fixes and enhancements ... snapshot user count" report ( issue #556 ) was fixed 2 years ago. Possibly this is another bug

;   int platformSensor;     short year ;     byte month;   ... .id. year , v.id.month, v.id.day, v.id.hour, v.value from PlatformSensor ps, Value v where ps.sensor.name like ?1 and v.id.platformSensor=ps.id and v.id. year =?2 and v.id.month=?3 and v.id.day=?4  

a university course on database technology. Last year we used odb104fe, and I was happy ... to me who have used Object databases for many years who are being lost due to a lack of JDO ... the ObjectDB product and company as a possible best and excellent solution to my persistence needs for at least the next five years . AlphaOne Ron Brennan

parameter used in both queries is obviously not the same. For the first query it is 1 year in the future, for the second query 1 year in the past. Otherwise there would be no bug. My provided test case

the problem. Note, however, that many issues have been fixed since version 2.6.3 (which is more than 3 years

the objectdb.jar file. When ObjectDB 2.0 was released many years ago, one appealing point

for this case? btc_es BTC EmbeddedSystems Hello, the BUG status is active since one year . But its not

would not need a change of the data model Yes, that makes sense. We will send you an invoice for one year