The better option in my opinion is a specific annotation ala
@Nationalized (https://hibernate.onjira.com/browse/HHH-5869). AFAIR We
were trying to see if the JPA expert group wanted to address this as
well and fall in line with whatever solution they decided on if so.
Probably best to just mov
The one in Configuration is the one used in the current code paths.
However the one in MetadataImpl will be used from 4.1 onward.
So both is best. It really should be trivial to change in both once
the actual thing to change to is in place.
On Tue 06 Sep 2011 12:19:09 PM CDT, Emmanuel Bernard
Damn so it looks like int he current codebase, identifierGeneratorFactory is
held both in MetadataImpl and Configuration. Do you know which one is currently
used in the codebase?
Should I make sure to update both?
On 6 sept. 2011, at 13:31, Emmanuel Bernard wrote:
> Hi all,
> I have the need to
Hi there,
as you know JDBC 4.0 now support unicode literal type, like NCHAR, NVARCHAR,
NCLOB, LONGNVARCHAR.
and there are lots of jiras asking we support these new types.
it is easy to create hibernate types for these jdbc type, for example, i have a
UnicodeStringType, so
@Entity
class Person{
jbott> Meeting ended Tue Sep 6 16:28:35 2011 UTC. Information about
MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2011/hibernate-dev.2011-09-06-15.03.html
Minutes (text):
http://transcripts.jboss.org/meeting
Better late than never:
+1 for Tuesday. Monday was always tricky for me anyways
On Mon, 29 Aug 2011 23:35:08 +0200, Steve Ebersole
wrote:
> Due to a change in schedule I can no longer do the meetings on Monday at
> the same time. To keep it on Monday we would need to move it back an
> hour w
On 6 September 2011 13:56, Hardy Ferentschik wrote:
> +1 for #2 for 4.0
>
> in the long run I like the simplicity of #3. I found #1 a bit of an
> overkill at least
> what I saw last in the discussion around this.
>
> --Hardy
Ok, follow up is HSEARCH-903
Sanne
On 6 sept. 2011, at 13:52, Sanne Grinovero wrote:
> On 6 September 2011 10:18, Emmanuel Bernard wrote:
>> Hi Sanne, Hardy and all,
>>
>> With Alpha 2 out last week it's time to enter the beta cycle.
>
> Just renamed Alpha3 to Beta1.
>
>> To get a CR1 as planned, we need to get a Beta1 out to
+1 for #2 for 4.0
in the long run I like the simplicity of #3. I found #1 a bit of an
overkill at least
what I saw last in the discussion around this.
--Hardy
On Tue, 06 Sep 2011 13:05:01 +0200, Sanne Grinovero
wrote:
> We need to take a decision regarding API changes to unlock the beta
On 6 September 2011 10:18, Emmanuel Bernard wrote:
> Hi Sanne, Hardy and all,
>
> With Alpha 2 out last week it's time to enter the beta cycle.
Just renamed Alpha3 to Beta1.
> To get a CR1 as planned, we need to get a Beta1 out to users by September
> 14th. That's going to be the only Beta.
> C
Hi all,
I have the need to implement https://hibernate.onjira.com/browse/HHH-6091 (Let
people customize identifier generator strategy mappings programmatically in
Hibernate 4)
and I am wondering why IdentifierGeneratorFactory is not a service and if it
would make sense for me to implement it as
We need to take a decision regarding API changes to unlock the beta releases;
so we should take a decision on this subject.
Summarizing the last proposals:
1) Use a builder API, which defines
- targeted entities
- enabled shard-aware filters
-- parameters on these filters
2) searchFactor
Hi Sanne, Hardy and all,
With Alpha 2 out last week it's time to enter the beta cycle.
To get a CR1 as planned, we need to get a Beta1 out to users by September 14th.
That's going to be the only Beta.
Can you take the lead on this? During this period I will be off.
I trust you can decide what
13 matches
Mail list logo
