Re: [Hibernate] Fetch profiles

2006-06-11 Thread Christian Bauer

On May 28, 2006, at 10:50 PM, Max Rydahl Andersen wrote:

> And I guess you really want it disjunct from the mapping and not  
> "just" where the assocation is already defined ?
>
> 
>   ...
>   
>...
>
>   
>
>   
> ...
> 
>   
> 
>
> Where the name could actually be comma seperated.
>
> Note that this construct doesn't prevent still having a
>  as a way to declare the association fetching
> independent on the declaration and of course the shared things.

In addition to these fetch profiles, how difficult would it be to  
expose dynamic cascading profiles? We discussed this several times in  
the past. IMO this has also been requested a few times and I've seen  
good use cases in real projects.



___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


[Hibernate] hibernate-sybase-testsuite Build Timed Out

2006-06-11 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sybase-testsuite?log=log20060611230700
BUILD TIMED OUTAnt Error Message: build timeoutDate of build: 06/11/2006 23:07:00Time to build: 




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (first 50 of 0)

___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


[Hibernate] hibernate-oracle10-testsuite Build Completed With Testsuite Errors

2006-06-11 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-oracle10-testsuite?log=log20060611224742
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:100: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:77: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 06/11/2006 22:47:42Time to build: 18 minutes 29 seconds




    Unit Tests: (850)    Total Errors and Failures: (12)testSequenceIdentityGeneratororg.hibernate.test.generatedkeys.seqidentity.SequenceIdentityTesttestParameterTypeMismatchFailsorg.hibernate.test.hql.ASTParserLoadingTesttestCriteriaAggregationReturnTypeFailureExpectedorg.hibernate.test.hql.CriteriaHQLAlignmentTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestReadOnlyOnProxiesFailureExpectedorg.hibernate.test.readonly.ReadOnlyTesttestEmptyInListFailureExpectedorg.hibernate.test.hql.HQLTesttestMaxindexHqlFunctionInElementAccessorFailureExpectedorg.hibernate.test.hql.HQLTesttestMultipleElementAccessorOperatorsFailureExpectedorg.hibernate.test.hql.HQLTesttestKeyManyToOneJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestDuplicateExplicitJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestOptimisticLockDirtyDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTesttestOptimisticLockAllDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTest 
 Modifications since last build: (first 50 of 0)

___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


[Hibernate] hibernate-timesten-testsuite Build Completed With Testsuite Errors

2006-06-11 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-timesten-testsuite?log=log20060611222346
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:93: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:77: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 06/11/2006 22:23:46Time to build: 23 minutes 0 seconds




    Unit Tests: (848)    Total Errors and Failures: (213)testCompositeIdsorg.hibernate.test.cid.CompositeIdTesttestNonLazyFetchorg.hibernate.test.cid.CompositeIdTesttestMultipleCollectionFetchorg.hibernate.test.cid.CompositeIdTesttestUpdateFalseorg.hibernate.test.component.ComponentTesttestComponentorg.hibernate.test.component.ComponentTesttestComponentFormulaQueryorg.hibernate.test.component.ComponentTesttestNamedQueryorg.hibernate.test.component.ComponentTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.AggressiveReleaseTesttestQueryScrollingorg.hibernate.test.connections.AggressiveReleaseTesttestConnectedSerializationorg.hibernate.test.connections.AggressiveReleaseTesttestManualDisconnectWithOpenResourcesorg.hibernate.test.connections.AggressiveReleaseTesttestConnectedSerializationorg.hibernate.test.connections.BasicConnectionProviderTesttestManualDisconnectWithOpenResourcesorg.hibernate.test.connections.BasicConnectionProviderTesttestSerializationFailsOnAfterStatementAggressiveReleaseWithOpenResourcesorg.hibernate.test.connections.CurrentSessionConnectionTesttestQueryScrollingorg.hibernate.test.connections.CurrentSessionConnectionTesttestConnectedSerializationorg.hibernate.test.connections.CurrentSessionConnectionTesttestManualDisconnectWithOpenResourcesorg.hibernate.test.connections.CurrentSessionConnectionTesttestConnectedSerializationorg.hibernate.test.connections.SuppliedConnectionTesttestManualDisconnectWithOpenResourcesorg.hibernate.test.connections.SuppliedConnectionTesttestScrollCriteriaorg.hibernate.test.criteria.CriteriaQueryTesttestRestrictionOnSubclassCollectionorg.hibernate.test.criteria.CriteriaQueryTesttestClassPropertyorg.hibernate.test.criteria.CriteriaQueryTesttestCompositeUserTypeorg.hibernate.test.cut.CompositeUserTypeTesttestDom4jorg.hibernate.test.dom4j.Dom4jTesttestMapIndexEmisionorg.hibernate.test.dom4j.Dom4jTesttestOrphanDeleteorg.hibernate.test.extralazy.ExtraLazyTesttestIndexFormulaMaporg.hibernate.test.extralazy.ExtraLazyTesttestJdkEnumStyleEnumConstantorg.hibernate.test.hql.ASTParserLoadingTesttestParameterTypeMismatchFailsorg.hibernate.test.hql.ASTParserLoadingTesttestCollectionJoinsInSubselectorg.hibernate.test.hql.ASTParserLoadingTesttestCollectionFetchWithDistinctionAndLimitorg.hibernate.test.hql.ASTParserLoadingTesttestNestedCollectionFetchorg.hibernate.test.hql.ASTParserLoadingTesttestSelectClauseSubselectorg.hibernate.test.hql.ASTParserLoadingTesttestImplicitPolymorphismorg.hibernate.test.hql.ASTParserLoadingTesttestCoalesceorg.hibernate.test.hql.ASTParserLoadingTesttestStrorg.hibernate.test.hql.ASTParserLoadingTesttestCastorg.hibernate.test.hql.ASTParserLoadingTesttestExtractorg.hibernate.test.hql.ASTParserLoadingTesttestOneToManyFilterorg.hibernate.test.hql.ASTParserLoadingTesttestSelectExpressionsorg.hibernate.test.hql.ASTParserLoadingTesttestWhereorg.hibernate.test.hql.ASTParserLoadingTesttestEntityFetchingorg.hibernate.test.hql.ASTParserLoadingTesttestCollectionFetchingorg.hibernate.test.hql.ASTParserLoadingTesttestStandardFunctionsorg.hibernate.test.hql.ASTParserLoadingTesttestDynamicInstantiationQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestResultTransformerScalarQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestResultTransformerEntityQueriesorg.hibernate.test.hql.ASTParserLoadingTesttestEJBQLFunctionsorg.hibernate.test.hql.ASTParserLoadingTesttestSubselectBetweenorg.hibernate.test.hql.ASTParserLoadingTesttestTempTableGenerationIsolationorg.hibernate.test.hql.BulkManipulationTesttestSimpleInsertorg.hibernate.test.hql.BulkManipulationTesttestSimpleNativeSQLInsertorg.hibernate.test.hql.BulkManipulationTesttestInsertWithManyToOneorg.hibernate.test.hql.BulkManipulationTesttestInsertWithMismatchedTypesorg.hibernate.test.hql.BulkManipulationTesttestInsertIntoSuperclassPropertiesFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertAcrossMappedJoinFailsorg.hibernate.test.hql.BulkManipulationTesttestInsertWithGeneratedIdorg.hibernate.test.hql.BulkManipulationTesttestInsertWithGeneratedVersionAndIdorg.hibernate.test.hql.BulkManipulationTesttestInsertWithGeneratedTimestampVersionorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnDiscriminatorSubclassorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnAnimalorg.hibernate.test.hql.BulkManipulationTesttestUpdateOnMam

[Hibernate] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors

2006-06-11 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060611221431
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:86: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:77: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 06/11/2006 22:14:31Time to build: 8 minutes 43 seconds




    Unit Tests: (848)    Total Errors and Failures: (11)testParameterTypeMismatchFailsorg.hibernate.test.hql.ASTParserLoadingTesttestCriteriaAggregationReturnTypeFailureExpectedorg.hibernate.test.hql.CriteriaHQLAlignmentTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestReadOnlyOnProxiesFailureExpectedorg.hibernate.test.readonly.ReadOnlyTesttestEmptyInListFailureExpectedorg.hibernate.test.hql.HQLTesttestMaxindexHqlFunctionInElementAccessorFailureExpectedorg.hibernate.test.hql.HQLTesttestMultipleElementAccessorOperatorsFailureExpectedorg.hibernate.test.hql.HQLTesttestKeyManyToOneJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestDuplicateExplicitJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestOptimisticLockDirtyDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTesttestOptimisticLockAllDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTest 
 Modifications since last build: (first 50 of 0)

___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


Re: [Hibernate] questions regarding development setup

2006-06-11 Thread Gavin King



Is there some actual problem we are trying to solve 
here? Because if there is, no-one has pointed it out yet.
 
The point of the failing tests is to remind and nag us to 
get them fixed. If we hide the failures we remove that 
incentive.
 
There has been a bunch of handwaving about how this could 
theoretically be a problem for continuous integration ... except that 
we are doing continuous integration and it is not causing 
any problems!
 
It seems there are some people here who have read a 
couple of books by Kent Beck and think that their job as a software 
developer is to enforce their Holy Perfect Process on everyone. That's perfectly 
fine, but we are practical people running an actual serious software project 
here, and we don't have time for trying to impress people by how aGiLe we 
are.
 
Thanks for your input, this is the end of 
the thread.


From: 
[EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Erik 
BertelsenSent: Sunday, June 11, 2006 12:35 PMTo: Max 
AndersenCc: hibernate-devel@lists.sourceforge.netSubject: 
Re: [Hibernate] questions regarding development setup

2006/6/11, Max Rydahl Andersen <[EMAIL PROTECTED]>:
as 
  i mentioned at the bug we could actually implement this by doing acustom 
  impl of HibernateTestCase.runTest()/max
Hi all,what about a version of runTest() that silently 
accepts test failures for tests that are expected to fail and report them as 
'failures' if they suddenly start to succeed. This will have the intended 
result that a test run is silent if everything works out as expected and if a 
test that is expected to fail suddenly succeeds, it will show up in the test 
report.If the success of the test was intentional because the problem was 
solved, the test should of course be changed to a normal non-failure-expected 
test. If the success was an unintentional consequence of some code change, then 
the developer can investigate whether the problem was really solved or just 
disguised and possibly alter the test. - 
Erik
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


Re: [Hibernate] questions regarding development setup

2006-06-11 Thread Max Rydahl Andersen
On Sun, 11 Jun 2006 18:34:36 +0200, Erik Bertelsen  
<[EMAIL PROTECTED]> wrote:

> 2006/6/11, Max Rydahl Andersen <[EMAIL PROTECTED]>:
>>
>>
>>
>> as i mentioned at the bug we could actually implement this by doing a
>> custom impl of HibernateTestCase.runTest()
>>
>> /max
>
>
>
> Hi all,
>
> what about a version of runTest() that silently accepts test failures for
> tests that are expected to fail and report them as 'failures' if they
> suddenly start to succeed.

that was the idea.

-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


Re: [Hibernate] questions regarding development setup

2006-06-11 Thread Erik Bertelsen
2006/6/11, Max Rydahl Andersen <[EMAIL PROTECTED]>:
as i mentioned at the bug we could actually implement this by doing acustom impl of HibernateTestCase.runTest()/maxHi all,what about a version of runTest() that silently accepts test failures for tests that are expected to fail and report them as 'failures' if they suddenly start to succeed.
This will have the intended result that a test run is silent if everything works out as expected and if a test that is expected to fail suddenly succeeds, it will show up in the test report.If the success of the test was intentional because the problem was solved, the test should of course be changed to a normal non-failure-expected test. If the success was an unintentional consequence of some code change, then the developer can investigate whether the problem was really solved or just disguised and possibly alter the test.
- Erik
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


Re: [Hibernate] questions regarding development setup

2006-06-11 Thread Max Rydahl Andersen
On Sun, 11 Jun 2006 00:56:38 +0200, Szczepan Faber <[EMAIL PROTECTED]>  
wrote:

> JUnit 4.x has @Ignore annotation.

and does not run on jdk 1.4, so what is the point ? :)

as i mentioned at the bug we could actually implement this by doing a  
custom impl of HibernateTestCase.runTest()

/max

>
> On 6/10/06, Scott M Stark <[EMAIL PROTECTED]> wrote:
>>
>> Then we need to fix it.
>> http://jira.jboss.com/jira/browse/JBQA-383
>>
>> > -Original Message-
>> > From: Max Andersen
>> > Sent: Saturday, June 10, 2006 10:21 AM
>> > To: Scott M Stark; Szczepan Faber
>> > Cc: hibernate-devel@lists.sourceforge.net
>> > Subject: RE: [Hibernate] questions regarding development setup
>> >
>> >
>> > Yes, but no such thing exist AFAIK. That is why we introduced
>> > this failureExpected notion.
>> >
>> > /max
>>



-- 
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]


___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel


[Hibernate] hibernate-hsqldb-testsuite Build Completed With Testsuite Errors

2006-06-11 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-hsqldb-testsuite?log=log20060611025307
TESTS FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:86: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-hibernate-db-matrix.xml:77: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 06/11/2006 02:53:07Time to build: 10 minutes 7 seconds




    Unit Tests: (848)    Total Errors and Failures: (11)testParameterTypeMismatchFailsorg.hibernate.test.hql.ASTParserLoadingTesttestCriteriaAggregationReturnTypeFailureExpectedorg.hibernate.test.hql.CriteriaHQLAlignmentTesttestReturnPropertyComponentRenameorg.hibernate.test.legacy.SQLLoaderTesttestReadOnlyOnProxiesFailureExpectedorg.hibernate.test.readonly.ReadOnlyTesttestEmptyInListFailureExpectedorg.hibernate.test.hql.HQLTesttestMaxindexHqlFunctionInElementAccessorFailureExpectedorg.hibernate.test.hql.HQLTesttestMultipleElementAccessorOperatorsFailureExpectedorg.hibernate.test.hql.HQLTesttestKeyManyToOneJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestDuplicateExplicitJoinFailureExpectedorg.hibernate.test.hql.HQLTesttestOptimisticLockDirtyDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTesttestOptimisticLockAllDeleteFailureExpectedorg.hibernate.test.optlock.OptimisticLockTest 
 Modifications since last build: (first 50 of 0)

___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel