HHH-2403 - import.sql improvement
by Łukasz Antoniak
Welcome!
Last time I have been trying to improve the way that Hibernate extracts
statements from "import.sql" script. My intention was to support
multiline SQL instructions (HHH-2403), quoted strings, multiline
comments etc. After developing quite simple ANTLR-based parser, I have
realized that right now semicolons are not mandatory (at the end of each
SQL statement). If there is no separator character (e.g. ';') between
statements, the only possibility to resolve HHH-2403 is to apply a full
SQL parser. But supporting all different dialects would be quite
difficult... Is it acceptable to change the code, so that each statement
must be ended with a semicolon (branch 4.0)?
You can see my work here:
https://github.com/lukasz-antoniak/hibernate-core/commit/c11b881a8975502f...
Regards,
Lukasz Antoniak
13 years, 1 month
meeting tomorrow
by Steve Ebersole
I will not be able to make the meeting tomorrow. I think the only real
pressing thing on the docket would have been 4.0 Final go/no-go. I
think we are good to go for Final. We can just discuss that via email.
Or, y'all can still have a meeting if there are other things you would
like to discuss. Someone would just need to "chair it" with jbott for
minutes/logging.
--
steve(a)hibernate.org
http://hibernate.org
13 years, 1 month
Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core
by Emmanuel Bernard
Yep, we have it running against 3.1.0.Beta3 which is the latest release published.
On 7 nov. 2011, at 17:27, David M. Lloyd wrote:
> I can look into it tonight. Have you tested with the latest 3.1.0 release to verify there are no problems?
>
> On 11/07/2011 09:51 AM, Steve Ebersole wrote:
>> Specifically, is there anyway to get org.jboss.logging:jboss-logging to
>> Final/GA in the next few days? The generator/processor is irrelevant as
>> far as we are concerned for a Hibernate release.
>>
>> On Mon 07 Nov 2011 09:47:08 AM CST, Steve Ebersole wrote:
>>> Which really sucks since 4.0 Final is slated for 2 days.
>>>
>>> Ugh.
>>>
>>> On Fri 04 Nov 2011 10:59:24 AM CDT, Emmanuel Bernard wrote:
>>>> Do you know when JBoss Logging 3.1.0.GA will hit the road. I can't
>>>> really release Hibernate Commons Annotations nor Core etc until we
>>>> have the final version. I mean we could but we might have to redo it.
>>>>
>>>> Emmanuel
>>>>
>>>> On 4 nov. 2011, at 16:05, David M. Lloyd wrote:
>>>>
>>>>> Yeah let's target 3.1.0.GA for everything. The final 1.0.0.GA release
>>>>> of the i18n logging tool will require 3.1.0.GA.
>>>>>
>>>>> On 11/04/2011 09:42 AM, Scott Marlow wrote:
>>>>>> Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
>>>>>> Hibernate (Core) module. The "org.jboss.logging" module happens to be
>>>>>> "3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
>>>>>> sync with the AS7 version of JBoss Logging.
>>>>>>
>>>>>> https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
>>>>>>
>>>>>>
>>>>>> I think that AS7 needs to stay in sync with what integrated
>>>>>> projects are
>>>>>> using (using the 3.1.0.* versions of JBoss logging for AS 7.1).
>>>>>>
>>>>>>
>>>>>> On 11/04/2011 07:30 AM, Emmanuel Bernard wrote:
>>>>>>> JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
>>>>>>> Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
>>>>>>>
>>>>>>> // logging
>>>>>>> logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
>>>>>>> logging_generator:
>>>>>>> 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
>>>>>>> logging_processor:
>>>>>>> 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
>>>>>>>
>>>>>>> So which one we should go to? Once we have decided, I will align
>>>>>>> Search, OGM and Commons Annotations.
>>>>>>>
>>>>>>> Emmanuel
>>>>>>> _______________________________________________
>>>>>>> hibernate-dev mailing list
>>>>>>> hibernate-dev(a)lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>>
>>>>> --
>>>>> - DML
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>>
>>>> _______________________________________________
>>>> hibernate-dev mailing list
>>>> hibernate-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
>
>
> --
> - DML
13 years, 1 month
Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core
by Emmanuel Bernard
Do you know when JBoss Logging 3.1.0.GA will hit the road. I can't really release Hibernate Commons Annotations nor Core etc until we have the final version. I mean we could but we might have to redo it.
Emmanuel
On 4 nov. 2011, at 16:05, David M. Lloyd wrote:
> Yeah let's target 3.1.0.GA for everything. The final 1.0.0.GA release
> of the i18n logging tool will require 3.1.0.GA.
>
> On 11/04/2011 09:42 AM, Scott Marlow wrote:
>> Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
>> Hibernate (Core) module. The "org.jboss.logging" module happens to be
>> "3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
>> sync with the AS7 version of JBoss Logging.
>>
>> https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
>>
>> I think that AS7 needs to stay in sync with what integrated projects are
>> using (using the 3.1.0.* versions of JBoss logging for AS 7.1).
>>
>>
>> On 11/04/2011 07:30 AM, Emmanuel Bernard wrote:
>>> JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
>>> Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
>>>
>>> // logging
>>> logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
>>> logging_generator: 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
>>> logging_processor: 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
>>>
>>> So which one we should go to? Once we have decided, I will align Search, OGM and Commons Annotations.
>>>
>>> Emmanuel
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>
> --
> - DML
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
13 years, 1 month
Fwd: Re: [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core
by Scott Marlow
-------- Original Message --------
Subject: Re: [jboss-as7-dev] [hibernate-dev] Which JBoss Logging version
to use in AS and Hibernate Core
Date: Fri, 04 Nov 2011 10:05:21 -0500
From: David M. Lloyd <david.lloyd(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Yeah let's target 3.1.0.GA for everything. The final 1.0.0.GA release
of the i18n logging tool will require 3.1.0.GA.
On 11/04/2011 09:42 AM, Scott Marlow wrote:
> Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
> Hibernate (Core) module. The "org.jboss.logging" module happens to be
> "3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
> sync with the AS7 version of JBoss Logging.
>
> https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
>
> I think that AS7 needs to stay in sync with what integrated projects are
> using (using the 3.1.0.* versions of JBoss logging for AS 7.1).
>
>
> On 11/04/2011 07:30 AM, Emmanuel Bernard wrote:
>> JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
>> Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
>>
>> // logging
>> logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
>> logging_generator: 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
>> logging_processor: 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
>>
>> So which one we should go to? Once we have decided, I will align Search, OGM and Commons Annotations.
>>
>> Emmanuel
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
13 years, 1 month
Which JBoss Logging version to use in AS and Hibernate Core
by Emmanuel Bernard
JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
// logging
logging: 'org.jboss.logging:jboss-logging:3.1.0.Beta3',
logging_generator: 'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
logging_processor: 'org.jboss.logging:jboss-logging-processor:1.0.0.CR3',
So which one we should go to? Once we have decided, I will align Search, OGM and Commons Annotations.
Emmanuel
13 years, 1 month
whitespace and formatting
by Sanne Grinovero
Hi all,
I'm used to methods formatting like this in the code:
gridDialect.removeAssociation( getCollectionMetadataKey() );
but some code is increasingly being written as
gridDialect.removeAssociation(getCollectionMetadataKey());
All options are fine for me, but can we pick one and stick to it?
I'd prefer the first one as that's how all code in Search is, and I
got used to it; it's also what is mandated by the Hibernate templates
for Eclipse (no idea what is in the IDEA templates).
Cheers,
Sanne
13 years, 1 month
Unique key constraint
by Ankita Patil
Hi,
I already have an id as the primary key for the table say XYZ.
Now, I want to set a field or a combination of two fields as a unique key
so that when i try to save say 2 entries in the DB with same value for the
unique key field then only one entry should be made in the table with one
primary key. I want hibernate to handle it internally and not throw me an
exception.
Now i have only one auto-generated primary key and when i try to save 2
entries in the DB with same value for the unique key field it stores
duplicate entries.
Is it possible? If yes how?
Thanks in advance
Ankita.
13 years, 1 month
