Guys,
Could someone please review the diff attached on EJB-395 ? If it looks good,
I'll commit to trunk and run the tests for all supported databases.
http://opensource.atlassian.com/projects/hibernate/browse/EJB-395
http://opensource.atlassian.com/projects/hibernate/secure/attachment/14215/Chan
Guys,
This is the one which originated the changes in the parent Test class for
Entity Manager, but somehow we managed to forget it :-) So, after discussing
the approaches, I did a new diff to replace the old one, which uses the
parent's capabilities on handling the sessions and exceptions.
N
- "Emmanuel Bernard" <[EMAIL PROTECTED]> escreveu:
> Cool
> On the other hand now I have to suffer Maven. So not so cool.
By the way, are we considering, even remotely, moving away from Maven? I mean,
this is probably not feasible in short term, but there are good options today
that are wort
- "Hardy Ferentschik" <[EMAIL PROTECTED]> escreveu:
> Knowing that I might open pandora's box now - what alternatives are
> you talking about?
> I assume you are not referring to ant/ivy.
I'm not :-) I don't like XML at all. As the wise man said: XML is like
violence. If it doesn't solve your
Guys,
How should I proceed with suggestions for Hibernate Search documentation
changes? Should I open a JIRA item for each item, with a diff? Who should I
assign them too? May I assign it to myself and commit the changes after getting
an OK from someone?
Examples:
Item 1.4:
In the code sample
All,
I'm about to making some patches to fix tests which uses table/column names
which are keywords for some RDBMS's. So, which branches should I target to,
when making such patches?
My initial list (for trunk, but similar ones for ANN/EM):
trunk
Branch_3_2
Branch_3_2_4_SP1_CP
Should I includ
All,
Hudson jobs for trunk are failing due to a dependency missing:
Path to dependency:
1) org.hibernate:hibernate-tutorials:pom:3.4.0-SNAPSHOT
2) org.slf4j:jcl-over-slf4j:jar:1.4.2
I got this error on my local setup too, when building the tutorials module. I
changed the pom.
All,
I don't know if this was discussed before (I didn't find it in the list's
archives), but if so, I'm probably missing something basic here :-)
I came across this issue, and I don't know whether this should be changed or
not. The problem is that the guy is trying to use the concat function
- "Thamayanthi k" <[EMAIL PROTECTED]> escreveu:
> I didn't understand what you are asking?
I can help you on getting your environment properly set if you join us on IRC,
channel #hibernate-dev, on freenode network (irc.freenode.net).
- Juca.
___
h
Guys,
This is not new, but I realized that it is happening in trunk. We fixed in
3_2-related branches, so, I applied the same logic, but changing some things:
- It now marks the test as "fail" if the test case leaves a transaction opened.
Of course, it also closes the transaction.
- It logs a w
Guys,
As suggested in a previous topic, I'll pay a genuine Czech beer in any pub in
Brno for whoever reviews the patch in HHH-3650[1] (or Moravian wine, if you
prefer) :-)
The class org.hibernate.id.enhanced.TableGenerator is used to generate tables
which acts as sequences. In the method sqlCr
- "Chris Bredesen" escreveu:
> The not null constraint is redundant in Oracle and possibly others;
> you
> wind up with two constraints on the table if you specify PK & not
> null.
I don't think so. I tested in our QA lab in both Oracle 9i and 10g. Only one
constraint and only one index. T
- "Steve Ebersole" escreveu:
> I am surprised that DB2 does not allow nulls and yet forces you to
> specify "not null" since it is totally redundant: PK cannot be null
> on
> DB2 by definition yet it forces user to explicitly specify "not null"
Not only that: they even have a very specific er
- "Steve Kuo" escreveu:
> I'm trying to build branch 3.3 using Maven and Java 1.5. I've followed
> the Maven build instructions (http://www.hibernate.org/422.html)
> exactly. When I build it fails on:
>
> Tests in error:
>
> [ERROR] BUILD FAILURE
Steve,
I think this question is more suita
14 matches
Mail list logo