http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-06-20-15.01.html
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-06-20-15.01.log.html
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibe
Hi Sanne,
On Thu, Jun 20, 2013 at 6:45 PM, Sanne Grinovero wrote:
> Great, so maybe we should just do that.
Yep, looks like a good idea and would be far cleaner.
--
Guillaume
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.
On 20 Jan 2013, at 6:22 PM, Guillaume Smet wrote:
> Hi,
>
> We would like to declare our global @AnalyzerDefs on a class which
> isn't a specific entity.
>
> For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
> a class annotated with @MappedSuperClass but with @AnalyzerDefs
Great, so maybe we should just do that.
BTW, slightly unrelated, but in the same style it always bothered me
that @NamedQuery definitions need to be specified on entities.
Granted they often relate to a specific entity, but not always, and in
some cases they are better maintained close to their bu
On 20 Jan 2013, at 6:39 PM, Sanne Grinovero wrote:
> Hardy, while moving to Jandex would it be possible - and efficient -
> for us to just find all @AnalyzerDefs on the user classpath (without
> these necessarily needing to be mapped entities) ?
Absolutely!
--Hardy
Hi Guillame,
reusing a @MappedSuperClass annotated entity sounds like a workaround
rather than the proper solution.
But I see your point on defining the global analyzers in a centralized
place rather than have them scattered on entities; question is if we
can do better?
There is a property to def
Hi,
We would like to declare our global @AnalyzerDefs on a class which
isn't a specific entity.
For the @TypeDefs of Hibernate, we do it by declaring the @TypeDefs on
a class annotated with @MappedSuperClass but with @AnalyzerDefs, we
are forced to declare them on a concrete @Entity.
Is this an
Hi,
I've created https://github.com/txtr/hibernate-delta because I couldn't
find a solution that would generate SQL update statements based on the
fields that I added to my @Entity.
The trick is that it stores the schema in an XML file that is commited
to git. That way, you only get the differe
