Here's what I'd like to do. In 4.1.x, all of the unique
constraint/index/column changes from HHH-7797 [1] and the random constraint
names in HHH-1904 [2] will be reverted. When we originally started working on
them, they weren't intended to be this complex. We'll cut a new 4.1.x release.
Bu
Create a remote in the clone of your fork that refers to the upstream
Hibernate repo:
* git remote add upstream git://github.com/hibernate/hibernate-orm.git
fetch the 4.2 branch into your clone:
* git fetch upstream 4.2:4.2
You can choose to push this to your fork or not. If so (assuming you
Hello hibernate developers,
I want to open a JIRA-Issue and as always I like to provide an according
test-case in form of a pull-request.
I already created pull-requests in past, but now I need to update/align my
fork of hibernate-orm with branch 4.2 which at the time of fork-creation did
not
Hi Brett,
On Fri, Apr 5, 2013 at 2:38 AM, Brett Meyer wrote:
> One other issue was pointed out:
> https://hibernate.atlassian.net/browse/HHH-8092?focusedCommentId=50658&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-50658
Oh, yeah. I started the application only o
