About YEAR

11-20 of 66Refresh
Issue
1

Negative snapshot user count exception

again. Since your system ran with ObjectDB for a long time (I think 2 years?) without these issues ... data. Rolling back to 2.3.x would be a problem because development work I did this year relies ... count" report (issue #556) was fixed 2 years ago. Possibly this is another bug that produces
Issue
1

ObjectDB 2 JDO Manual

of an object database in a university course on database technology. Last year we used odb104fe, and I ... Object databases for many years who are being lost due to a lack of JDO documentation. 1) makes ... best and excellent solution to my persistence needs for at least the next five years. geekox86 carr.onstott FredrikB AlphaOne
Forum
1

ObjectDB future

Hi, For how long ObjectDB will exist and will be actively maintained? Will it still be there in 10 years? In 20 years? Thanks. 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 is unstable and many
Forum
1

Getting sales quantity per country with a query, an idea anyone?

, monthBack + 1);         to.set(to.get(Calendar.YEAR), to.get(Calendar.MONTH), 1 ... .MONTH, monthBack);         from.set(from.get(Calendar.YEAR), from.get(Calendar.MONTH), 1
Forum
1

Great product - needs better marketing - more popularity

on ObjectDB since the beginning of this year, but I think it would be much better if your db was more popular ... and object DBMSs for over thirty years. I'm currently building foundation frameworks and classes
Forum
1

Homepage and forum nearly inaccessible

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

JRebel integration feature

to save me months of development time per year, and it helps avoid a lot of frustration, enabling ... , for the first time in years (I had tried JRebel many times before but the clashes with ObjectDB
Forum
1

Mismatch client-server protocol prefix

result;     } This code worked for a couple of years now and is used in multiple projects. Looks ... the Doctor. It found no errors. We use this method for over 3 years now. It's from the early days
Issue
1

Bug when using SIZE in combination with date lower parameter

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 illustrates
Issue
1

each 1-2 days objects on some objectdb level lock/block each other

through our private priority support, which costs 2,400 GBP per year. As many of the issues ... for one year priority support tomorrow. Please create a new private support ticket for the optimisation