I've signed up for a "test drive" account on Atlassian's Stride server.
Stride is their replacement for HipChat.
-- Forwarded message -
From: Stride by Atlassian
Date: Tue, Oct 24, 2017, 1:32 PM
Subject: You're on the Stride waitlist!
To:
[image: Stride by Atlassian]
Nice! Yo
On Tue, Oct 24, 2017 at 8:38 AM Gunnar Morling wrote:
> Sure. But it's great to know that you'd find it useful and can imagine
> adding it. Thanks!
>
In fact we have similar requirement in ORM itself for hibernate-envers,
but again the initial expectation is supporting this at the boot-model
le
Hi!
Here are the minutes of this week's NoORM IRC meeting:
16:05 < jbott> Meeting ended Tue Oct 24 14:05:39 2017 UTC.
Information about MeetBot at http://wiki.debian.org/MeetBot . (v
0.1.4)
16:05 < jbott> Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2017/hibernate-d
2017-10-24 15:08 GMT+02:00 Steve Ebersole :
> Of course you pick the easy case to illustrate :) A single entity with
> nothing but basic attributes or self-referential associations is going to
> be relatively simple. The trickier stuff is adding 2 entities with
> association between them, "prope
Of course you pick the easy case to illustrate :) A single entity with
nothing but basic attributes or self-referential associations is going to
be relatively simple. The trickier stuff is adding 2 entities with
association between them, "property-ref" FKs, etc. Then your fluent API is
not so fl
That would be great for framework developers as well.
Il 24 ott 2017 12:01, "Gunnar Morling" ha scritto:
> Anyone with thoughts on this? To elaborate, here's what I have in mind:
>
> EntityMapping mapping = session.addEntityMapping();
> mapping.entity( Person.class )
> .table( "P
Anyone with thoughts on this? To elaborate, here's what I have in mind:
EntityMapping mapping = session.addEntityMapping();
mapping.entity( Person.class )
.table( "PERSONS" )
.property( "personId" )
.id()
.strategy( Strategy.IDENTITY )
.p
