DAO Fusion Google Group

Re: Question concerning Bitemporal History

igor.miha...@gmail.com (Igor Mihalik) — Wed, 16 Mar 2011 10:40:39 UT

Hi Nico,

I think that you got a little further than we did. We were aware of
these disadvantages of Hibernate collection loading but we did not get
into the optimization phase. We had couple of reasons for that:
1. we were developing an application that relied on bitemporal and we
did not encounter tremendous performance issues. I'm not saying that

Re: Question concerning Bitemporal History

nico.roga...@gmail.com (Nico R.) — Tue, 15 Mar 2011 23:31:19 UT

Hi Igor,
So changing all the historic get statements worked like a charm,
specially when utilising the Persistent entity criteria API DAO
provides.
But when it comes to the set() method of adding to the trace and
manipulating the history I get stuck on Hibernates stupid lazy loading
character.

Re: [dao-fusion] Re: Question concerning Bitemporal History

igor.miha...@gmail.com (Igor Mihálik) — Mon, 14 Mar 2011 16:24:48 UT

Hi Nico,
no problem, sorry for delayed response I was a little busy with other stuff
last week. If git is a problem to use I advice you to create a patch and
attach to either this thread or preferably create an issue (
[link] ) and attach it over there.
We'll definitely look at it and include it in the trunk. Basically the only

Re: Question concerning Bitemporal History

nico.roga...@gmail.com (Nico R.) — Sun, 13 Mar 2011 22:44:10 UT

Hmm long time no answer, maybe I was a little harsh in my
complaints? ;o)
But I'm not here to complain, but to improve when it's nessesary. So I
checked out the dao fusion project from googlecode and put some effort
into reducing the described boilerplate and switching the selects of
bitemps from object based (asking the trace list) to DB based.

Re: Question concerning Bitemporal History

nico.roga...@gmail.com (Nico R.) — Tue, 08 Mar 2011 22:50:39 UT

I just mean the whole "value" Attribute declaration and the copyWith()
stuff in the specific BitemporalWrapper and the "hists" Attribute
declaration and getHists() stuff in the "Anchor".
I found a way now to generalize this stuff and put it in 2 abstract
superclasses "AbstractBitemporalModelWrappe r" and "AbstractAnchor" so

Re: Question concerning Bitemporal History

igor.miha...@gmail.com (Igor Mihalik) — Mon, 07 Mar 2011 16:46:05 UT

The bitemporal code has origins in the work of ervacon and with their
permission we were able to include the source and enhance it to use
JPA/Hibernate annotations instead of xml mapping files. You can find
the original code here: [link]

Regarding your question, what kind of simplifications do you have in

Re: Question concerning Bitemporal History

nico.roga...@gmail.com (Nico R.) — Fri, 04 Mar 2011 13:06:38 UT

Ahh yeah thanks,
I was aware of the left open, right closed time interval, my fault was
only to create an interval to save a new bitemp with
TimeUtils.interval(tt,TimeUtil s.endOfTime()) where I should have used
TimeUtils.from(tt).
So TimeUtils.endOfTime() is only intended for querying, but not for

Re: Question concerning Bitemporal History

igor.miha...@gmail.com (Igor Mihalik) — Wed, 02 Mar 2011 15:18:22 UT

Hi Nico,

the answer is quite simple and has to do with intervals. Both validity
and record intervals are defined as:
interval = <start, end) (notice the brackets, "end" is open).
Now image a scenario where you want to get all intervals (for example
information valid at "certain_time"). You'd iterate all intervals and

Question concerning Bitemporal History

nico.roga...@gmail.com (Nico R.) — Wed, 02 Mar 2011 14:12:57 UT

Hey guys,
first off compliments to this great project. Even though the
bitemporal History Implementation seems to be just a side issue, I
find the way of implementation and API Design very thoughtfull.

So I was trying out and testing some different scenarios of bitemporal
history and I found some weird finding when trying to compare the end

Re: Release Notes

vojtech.sz...@gmail.com (Vojtech Szocs) — Tue, 06 Oct 2009 14:42:25 UT

Hi everybody!

Our milestone journey towards next feature release is finally over -
DAO Fusion 1.2.0 has just been released.

We've managed to do some minor enhancements to M3 as well as
completing the step-by-step "Hello, DAO! tutorial" - give it a try:
[link]

Spam messages

vojtech.sz...@gmail.com (Vojtech Szocs) — Tue, 22 Sep 2009 07:42:42 UT

Hi everybody, unluckily to us, we keep receiving numerous spam
messages on our discussion group. If things keep going like so, we
will have to change our posting rules.

Re: Release Notes

vojtech.sz...@gmail.com (Vojtech Szocs) — Mon, 14 Sep 2009 12:11:00 UT

DAO Fusion team is happy to announce the release of third and last
milestone towards version 1.2.0.

The bitemporal pattern implementation is now fully integrated with
standard persistent entity model together with proper Javadocs and
reference documentation:
[link]

Re: Bitemporal pattern

vojtech.sz...@gmail.com (Vojtech Szocs) — Thu, 10 Sep 2009 08:53:58 UT

Hi Christian,

the reference documentation is now complete. You can take a look at
bitemporal pattern implementation details (and examples) here:
[link]

Let us know what you think. In the meantime, the third milestone and

Re: Bitemporal pattern

christian.bour...@gmail.com (Mr.C) — Wed, 09 Sep 2009 20:41:25 UT

Thanks a lot!

Re: Bitemporal pattern

vojtech.sz...@gmail.com (Vojtech Szocs) — Mon, 07 Sep 2009 09:09:44 UT

Hi Christian,

the bitemporal example (including code snippets) will be part of the
official bitemporal pattern reference documentation:
[link]

We will try to finish it as soon as possible.. We have the final
version nearly completed though.