On Sun, 31 Jul 2011 21:44:13 +0200, Sanne Grinovero sa...@hibernate.org
wrote:
In case you would have a
@ElementCollection
@Field(indexNullAsl=nullToken)
String[] tags
having the value {A,B,null}
I would expect this to be encoded in the index with three field
writes, all named tags,
On 31 juil. 2011, at 21:44, Sanne Grinovero wrote:
@ElementCollection
@Field(indexNullAsl=nullToken)
String[] tags
Hum is it really the way we are going? ie @Field would be used by the elements
of the collection if it's a collection?
I'm not a big fan for a couple of reasons:
- it breaks
On Mon, 01 Aug 2011 09:41:05 +0200, Emmanuel Bernard
emman...@hibernate.org wrote:
We're back to the same problem over and over but to me the best mapping
in Java 8 will be:
@ElementCollection
Collection@Field(bridge=StringBridge.class) String tags
right. same for HV and the ability to
2011/8/1 Emmanuel Bernard emman...@hibernate.org:
On 31 juil. 2011, at 21:44, Sanne Grinovero wrote:
@ElementCollection
@Field(indexNullAsl=nullToken)
String[] tags
Hum is it really the way we are going? ie @Field would be used by the
elements of the collection if it's a collection?
On 1 août 2011, at 10:31, Sanne Grinovero wrote:
2011/8/1 Emmanuel Bernard emman...@hibernate.org:
On 31 juil. 2011, at 21:44, Sanne Grinovero wrote:
@ElementCollection
@Field(indexNullAsl=nullToken)
String[] tags
Hum is it really the way we are going? ie @Field would be used by the
2011/8/1 Emmanuel Bernard emman...@hibernate.org:
On 1 août 2011, at 10:31, Sanne Grinovero wrote:
2011/8/1 Emmanuel Bernard emman...@hibernate.org:
On 31 juil. 2011, at 21:44, Sanne Grinovero wrote:
@ElementCollection
@Field(indexNullAsl=nullToken)
String[] tags
Hum is it really the
@Field(bridge=@FieldBridge(impl=CustomCollFB.class)
public CollectionString getNames() { ... }
I think this new bridge could be applied to the elements in this case,
but be overridden by a custom bridge: so if someone was defining his
own custom bridge it would still be applied instead.
2011/8/1 Emmanuel Bernard emman...@hibernate.org:
@Field(bridge=@FieldBridge(impl=CustomCollFB.class)
public CollectionString getNames() { ... }
I think this new bridge could be applied to the elements in this case,
but be overridden by a custom bridge: so if someone was defining his
own
On Mon, 01 Aug 2011 13:01:02 +0200, Sanne Grinovero sa...@hibernate.org
wrote:
@Field
@DateBridge(resolution=Resolution.DAY)
private SetDate views;
I think it's quite clear what the user meant to do, don't you?
I personally find it confusing that we reuse the same @Field at the
same
@IndexedEmbedded
@DateBridge(resolution=Resolution.DAY)
private SetDate views;
Of course this clashes in case people want both the proposed behavior
and use a custom field bridge in parallel. But such feature is not
supported by the currently proposed syntax either
That's great, it
[resending as the previous one was from the wrong account]
I find @IndexedEmbedded as ambiguous, besides you are adding an additional
annotation
since @ElementCollection is still there, right? Just saying there are
quite a few annotations.
I agree we should minimize the number of
On Mon, 01 Aug 2011 14:04:58 +0200, Emmanuel Bernard
emman...@hibernate.org wrote:
Note that @ElementCollection is the JPA annotation that might or might
not be present (HSearch on Infinispan doesn't use JPA annotations).
Right. I was just talking about the overall number of annotations
Begin forwarded message:
From: Davide D'Alto daltodav...@gmail.com
Date: 1 août 2011 14:29:57 HAEC
To: Emmanuel Bernard emman...@hibernate.org
Subject: Re: [hibernate-dev] [HSEARCH-566] Indexing null values for an
@ElementCollection
That's great, it is much cleaner. I was leaning for
jbott Meeting ended Mon Aug 1 16:18:43 2011 UTC. Information about
MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
jbott Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2011/hibernate-dev.2011-08-01-15.00.html
jbott Minutes (text):
Hi,
I just noticed that a PurgeAll request will ask the sharding strategy
to know to which shard it should be applied, using the following
method:
getDirectoryProvidersForDeletion(Class? entity, Serializable id,
String idInString) {
and passing in null for the second and third arguments.
That's
http://pastebin.com/SR3jsxGp contains the call stack for a
ClassNotFoundException of org.hibernate.hql.internal.ast.HqlToken (from
https://issues.jboss.org/browse/AS7-1433). The exception message isn't
shown but the jira has that.
I tried the supplied test case against Hibernate 4.0.0.Beta3
I fixed HHH-1780, may relates to this issue?
---
Strong Liu st...@hibernate.org
http://hibernate.org
http://github.com/stliu
On Aug 2, 2011, at 5:20 AM, Scott Marlow wrote:
http://pastebin.com/SR3jsxGp contains the call stack for a
ClassNotFoundException of
oh, the fix of HHH-1780 is not included in beta4
---
Strong Liu st...@hibernate.org
http://hibernate.org
http://github.com/stliu
On Aug 2, 2011, at 9:09 AM, Strong Liu wrote:
I fixed HHH-1780, may relates to this issue?
---
Strong Liu st...@hibernate.org
18 matches
Mail list logo
