You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2014/01/26 17:54:54 UTC

3.1 RC1?

Any objections if I assemble 3.1RC1 some time within the next week?

A.

Re: 3.1 RC1?

Posted by John Huss <jo...@gmail.com>.
Sounds good to me.

> On Feb 5, 2014, at 7:04 AM, Andrus Adamchik <an...@objectstyle.org> wrote:
> 
> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
> 
> hsql:        PASSED
> h2:        PASSED
> derby:        PASSED
> mysql 5.0:    PASSED (with the following config [1])
> mysql 5.6:    PASSED (with the following config [2])
> 
> postgres    Failures: 1, Errors: 0
>        testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
> 
> oracle 11:    Failures: 11, Errors: 9
> Failed tests: 
>  testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>  testLoad(org.apache.cayenne.access.DbLoaderTest)
>  testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
> 
> Tests in error: 
>  testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
> 
> 
> [1] MySQL 5.0 config:
>    [mysqld]
>    max_allowed_packet=16M
> 
> [2] MySQL 5.6 config:
>    [mysqld]
>    max_allowed_packet=16M
>    lower_case_table_names = 1
> 
> Andrus
>

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
Just did more cleanup of the unit tests and added SQLServer to the test matrix (and older 2005 Express version). I think I am finally done with tests and will go on to the release assembly for a vote...

Here is a new test scorecard. 

rat:         PASSED
hsql:        PASSED
h2:          PASSED
derby:       PASSED
derby/Java7: PASSED
mysql 5.0:   PASSED [1]
mysql 5.6:   PASSED [2]
sqlserver    PASSED [3]
postgresql   Failures: 1
             testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
oracle 11:   Failures: 9
             testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
             testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
             testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
             testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
             testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
             testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
             testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
             testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
             testLoad(org.apache.cayenne.access.DbLoaderTest)

[1] MySQL 5.0 config:
	[mysqld]
	max_allowed_packet=16M

[2] MySQL 5.6 config:
	[mysqld]
	max_allowed_packet=16M
	lower_case_table_names = 1

[3] SQL Server 2005 Expression config:
	collation - SQL_Latin1_general_CP1_CS_AS

Andrus

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
As expected, procedure test failures are caused by a problem in a test suite, not the underlying Cayenne code. Just fixed those and we are down to thee failures with Oracle:

Failed tests: 
  testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
  testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
  testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
  testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
  testLoad(org.apache.cayenne.access.DbLoaderTest)
  testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)

Tests run: 2148, Failures: 11, Errors: 0, Skipped: 0

I will see if I can knock down a few more failures on this list and will also try to setup SQLServer over the weekend and run some tests with it.

Andrus


On Feb 5, 2014, at 8:04 AM, Andrus Adamchik <an...@objectstyle.org> wrote:

> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
> 
> hsql:		PASSED
> h2:		PASSED
> derby:		PASSED
> mysql 5.0: 	PASSED (with the following config [1])
> mysql 5.6: 	PASSED (with the following config [2])
> 
> postgres	Failures: 1, Errors: 0
> 		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
> 
> oracle 11:	Failures: 11, Errors: 9
> Failed tests: 
>  testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>  testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>  testLoad(org.apache.cayenne.access.DbLoaderTest)
>  testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
> 
> Tests in error: 
>  testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>  testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
> 
> 
> [1] MySQL 5.0 config:
> 	[mysqld]
> 	max_allowed_packet=16M
> 
> [2] MySQL 5.6 config:
> 	[mysqld]
> 	max_allowed_packet=16M
> 	lower_case_table_names = 1
> 
> Andrus
> 
>

Re: 3.1 RC1?

Posted by Mike Kienenberger <mk...@gmail.com>.
I'm an oracle user.
I haven't had any oracle issues with 3.1

On Thu, Feb 6, 2014 at 5:22 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> I'm a traditionalist, but isn't "release candidate" a version ready for release? I haven't looked at the bugs below (and don't have Oracle installed anywhere since I dropped support for it in my products several years ago), but are they serious? Do we care about releasing with them?
>
> Maybe it is just splitting hairs, since rc has become the "new beta" for many projects. The purpose here is to get a wider audience and testing I guess. So that's a big plus.
>
> Do we have any regular Oracle users on this list? Are these errors just something do to with a particular Oracle driver mapping?
>
> Ari
>
>
> On 6/02/2014 12:04am, Andrus Adamchik wrote:
>> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
>>
>> hsql:         PASSED
>> h2:           PASSED
>> derby:                PASSED
>> mysql 5.0:    PASSED (with the following config [1])
>> mysql 5.6:    PASSED (with the following config [2])
>>
>> postgres      Failures: 1, Errors: 0
>>               testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
>>
>> oracle 11:    Failures: 11, Errors: 9
>> Failed tests:
>>   testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>   testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>>   testLoad(org.apache.cayenne.access.DbLoaderTest)
>>   testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
>>
>> Tests in error:
>>   testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>   testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
>>
>>
>> [1] MySQL 5.0 config:
>>       [mysqld]
>>       max_allowed_packet=16M
>>
>> [2] MySQL 5.6 config:
>>       [mysqld]
>>       max_allowed_packet=16M
>>       lower_case_table_names = 1
>>
>> Andrus
>>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: 3.1 RC1?

Posted by Richard Frovarp <rf...@apache.org>.
I could help out testing against Oracle if I knew what needed to be 
done. My uses are pretty simple, but I do use some of the data types 
that seem to be failing below.

On 02/06/2014 04:22 PM, Aristedes Maniatis wrote:
> I'm a traditionalist, but isn't "release candidate" a version ready for release? I haven't looked at the bugs below (and don't have Oracle installed anywhere since I dropped support for it in my products several years ago), but are they serious? Do we care about releasing with them?
>
> Maybe it is just splitting hairs, since rc has become the "new beta" for many projects. The purpose here is to get a wider audience and testing I guess. So that's a big plus.
>
> Do we have any regular Oracle users on this list? Are these errors just something do to with a particular Oracle driver mapping?
>
> Ari
>
>
> On 6/02/2014 12:04am, Andrus Adamchik wrote:
>> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
>>
>> hsql:		PASSED
>> h2:		PASSED
>> derby:		PASSED
>> mysql 5.0: 	PASSED (with the following config [1])
>> mysql 5.6: 	PASSED (with the following config [2])
>>
>> postgres	Failures: 1, Errors: 0
>> 		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
>>
>> oracle 11:	Failures: 11, Errors: 9
>> Failed tests:
>>    testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>    testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>>    testLoad(org.apache.cayenne.access.DbLoaderTest)
>>    testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
>>
>> Tests in error:
>>    testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>    testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
>>
>>
>> [1] MySQL 5.0 config:
>> 	[mysqld]
>> 	max_allowed_packet=16M
>>
>> [2] MySQL 5.6 config:
>> 	[mysqld]
>> 	max_allowed_packet=16M
>> 	lower_case_table_names = 1
>>
>> Andrus
>>
>

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
Also I personally treat RC as a production-ready label. Not as a gimmick to get testers :)

On Feb 6, 2014, at 5:27 PM, Andrus Adamchik <an...@objectstyle.org> wrote:

> I may need to dig through the procedure test failures, but ReturnTypesMappingTest IIRC is just Oracle not providing the metadata that we need. So we can’t make the right assertion. 
> 
> BTW all the recent commits on 3.1 branch were about unit test robustness. None of the failures I’ve dealt with in the past month were bugs in the code.
> 
> Andrus
> 
> On Feb 6, 2014, at 5:22 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> 
>> I'm a traditionalist, but isn't "release candidate" a version ready for release? I haven't looked at the bugs below (and don't have Oracle installed anywhere since I dropped support for it in my products several years ago), but are they serious? Do we care about releasing with them?
>> 
>> Maybe it is just splitting hairs, since rc has become the "new beta" for many projects. The purpose here is to get a wider audience and testing I guess. So that's a big plus.
>> 
>> Do we have any regular Oracle users on this list? Are these errors just something do to with a particular Oracle driver mapping?
>> 
>> Ari
>> 
>> 
>> On 6/02/2014 12:04am, Andrus Adamchik wrote:
>>> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
>>> 
>>> hsql:		PASSED
>>> h2:		PASSED
>>> derby:		PASSED
>>> mysql 5.0: 	PASSED (with the following config [1])
>>> mysql 5.6: 	PASSED (with the following config [2])
>>> 
>>> postgres	Failures: 1, Errors: 0
>>> 		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> 
>>> oracle 11:	Failures: 11, Errors: 9
>>> Failed tests: 
>>> testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>> testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>>> testLoad(org.apache.cayenne.access.DbLoaderTest)
>>> testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
>>> 
>>> Tests in error: 
>>> testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>> testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
>>> 
>>> 
>>> [1] MySQL 5.0 config:
>>> 	[mysqld]
>>> 	max_allowed_packet=16M
>>> 
>>> [2] MySQL 5.6 config:
>>> 	[mysqld]
>>> 	max_allowed_packet=16M
>>> 	lower_case_table_names = 1
>>> 
>>> Andrus
>>> 
>> 
>> -- 
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>> 
> 
>

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
I may need to dig through the procedure test failures, but ReturnTypesMappingTest IIRC is just Oracle not providing the metadata that we need. So we can’t make the right assertion. 

BTW all the recent commits on 3.1 branch were about unit test robustness. None of the failures I’ve dealt with in the past month were bugs in the code.

Andrus

On Feb 6, 2014, at 5:22 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> I'm a traditionalist, but isn't "release candidate" a version ready for release? I haven't looked at the bugs below (and don't have Oracle installed anywhere since I dropped support for it in my products several years ago), but are they serious? Do we care about releasing with them?
> 
> Maybe it is just splitting hairs, since rc has become the "new beta" for many projects. The purpose here is to get a wider audience and testing I guess. So that's a big plus.
> 
> Do we have any regular Oracle users on this list? Are these errors just something do to with a particular Oracle driver mapping?
> 
> Ari
> 
> 
> On 6/02/2014 12:04am, Andrus Adamchik wrote:
>> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
>> 
>> hsql:		PASSED
>> h2:		PASSED
>> derby:		PASSED
>> mysql 5.0: 	PASSED (with the following config [1])
>> mysql 5.6: 	PASSED (with the following config [2])
>> 
>> postgres	Failures: 1, Errors: 0
>> 		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
>> 
>> oracle 11:	Failures: 11, Errors: 9
>> Failed tests: 
>>  testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>>  testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>>  testLoad(org.apache.cayenne.access.DbLoaderTest)
>>  testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
>> 
>> Tests in error: 
>>  testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>>  testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
>> 
>> 
>> [1] MySQL 5.0 config:
>> 	[mysqld]
>> 	max_allowed_packet=16M
>> 
>> [2] MySQL 5.6 config:
>> 	[mysqld]
>> 	max_allowed_packet=16M
>> 	lower_case_table_names = 1
>> 
>> Andrus
>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>

Re: 3.1 RC1?

Posted by Aristedes Maniatis <ar...@maniatis.org>.
I'm a traditionalist, but isn't "release candidate" a version ready for release? I haven't looked at the bugs below (and don't have Oracle installed anywhere since I dropped support for it in my products several years ago), but are they serious? Do we care about releasing with them?

Maybe it is just splitting hairs, since rc has become the "new beta" for many projects. The purpose here is to get a wider audience and testing I guess. So that's a big plus.

Do we have any regular Oracle users on this list? Are these errors just something do to with a particular Oracle driver mapping?

Ari


On 6/02/2014 12:04am, Andrus Adamchik wrote:
> I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.
> 
> hsql:		PASSED
> h2:		PASSED
> derby:		PASSED
> mysql 5.0: 	PASSED (with the following config [1])
> mysql 5.6: 	PASSED (with the following config [2])
> 
> postgres	Failures: 1, Errors: 0
> 		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)
> 
> oracle 11:	Failures: 11, Errors: 9
> Failed tests: 
>   testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
>   testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
>   testLoad(org.apache.cayenne.access.DbLoaderTest)
>   testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)
> 
> Tests in error: 
>   testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
>   testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)
> 
> 
> [1] MySQL 5.0 config:
> 	[mysqld]
> 	max_allowed_packet=16M
> 
> [2] MySQL 5.6 config:
> 	[mysqld]
> 	max_allowed_packet=16M
> 	lower_case_table_names = 1
> 
> Andrus
> 

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
I just did some testing across various DBs, fixing a bunch of unit tests in the process. Below are the results. I think we should go with RC.

hsql:		PASSED
h2:		PASSED
derby:		PASSED
mysql 5.0: 	PASSED (with the following config [1])
mysql 5.6: 	PASSED (with the following config [2])

postgres	Failures: 1, Errors: 0
		testBLOB(org.apache.cayenne.access.ReturnTypesMappingTest)

oracle 11:	Failures: 11, Errors: 9
Failed tests: 
  testBIGINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBIT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBOOLEAN(org.apache.cayenne.access.ReturnTypesMappingTest)
  testDOUBLE(org.apache.cayenne.access.ReturnTypesMappingTest)
  testFLOAT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testREAL(org.apache.cayenne.access.ReturnTypesMappingTest)
  testSMALLINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testTINYINT(org.apache.cayenne.access.ReturnTypesMappingTest)
  testBindCHARInWHERE(org.apache.cayenne.query.SQLTemplateTest)
  testLoad(org.apache.cayenne.access.DbLoaderTest)
  testBindingForCollection(org.apache.cayenne.access.jdbc.BindDirectiveTest)

Tests in error: 
  testFetchLimit(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testSelect1(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testSelect2(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testSelect3(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testFetchOffset(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testColumnNameCapitalization(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testSelectDataObject(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testSelectWithRowDescriptor(org.apache.cayenne.access.DataContextProcedureQueryTest)
  testProcedureQueryStringMapBoolean(org.apache.cayenne.access.DataContextPerformQueryAPITest)


[1] MySQL 5.0 config:
	[mysqld]
	max_allowed_packet=16M

[2] MySQL 5.6 config:
	[mysqld]
	max_allowed_packet=16M
	lower_case_table_names = 1

Andrus

Re: 3.1 RC1?

Posted by Andrus Adamchik <an...@objectstyle.org>.
Hi Ari,

thanks for building this list. So.. 

CAY-1524 - I have no objections to fixing that in 3.1, before or after RC1. Or move it to 3.2 for that matter.
CAY-1480 - I just fixed it on 3.2
CAY-1470 - This is not fixed. I am not comfortable with the patches. Also latest Oracle drivers remove a bunch of non-standard hacks. Maybe we need to reeval this once more. In any event, not ready to put it in 3.1. 
CAY-1437 - This is a new feature. We can't include it in 3.1.
CAY-1210 Both 3.1 and 3.2 support 'cayenne.runtime.db.collation.assume.ci'. It was added on Sept 14, 2011, i.e. after the patches. I just added it to release notes and closed the Jira. Dima, feel free to correct me here… and / or open a follow up Jira if there are leftovers.

I don’t see anything on the list that warrants attention in 3.1. So let’s probably move the remaining ones to 3.2.

Andrus



On Jan 27, 2014, at 4:17 AM, Aristedes Maniatis <ar...@maniatis.org> wrote:

> I think it is a fine idea, but we should review Jira.
> 
> 1. If we abandon the idea of 3.1B3, then I'll merge this https://issues.apache.org/jira/browse/CAY/fixforversion/12324064 back to the 3.0(final) milestone here:
> 
> https://issues.apache.org/jira/browse/CAY/fixforversion/12316229
> 
> 2. There are still 29 open tasks in the 3.0 final milestone.
> 
> Obviously all the big feature requests should be moved on to the future, but some of the improvements actually already have patches. Like this:
> 
> https://issues.apache.org/jira/browse/CAY-1107
> 
> 
> I think it would be wise to first review these issues and either close/merge or move them on to future milestones.
> 
> Ari
> 
> 
> 
> On 27/01/2014 3:54am, Andrus Adamchik wrote:
>> Any objections if I assemble 3.1RC1 some time within the next week?
>> 
>> A.
>> 
> 
> -- 
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A
>

Re: 3.1 RC1?

Posted by Aristedes Maniatis <ar...@maniatis.org>.
I think it is a fine idea, but we should review Jira.

1. If we abandon the idea of 3.1B3, then I'll merge this https://issues.apache.org/jira/browse/CAY/fixforversion/12324064 back to the 3.0(final) milestone here:

https://issues.apache.org/jira/browse/CAY/fixforversion/12316229

2. There are still 29 open tasks in the 3.0 final milestone.

Obviously all the big feature requests should be moved on to the future, but some of the improvements actually already have patches. Like this:

https://issues.apache.org/jira/browse/CAY-1107


I think it would be wise to first review these issues and either close/merge or move them on to future milestones.

Ari



On 27/01/2014 3:54am, Andrus Adamchik wrote:
> Any objections if I assemble 3.1RC1 some time within the next week?
> 
> A.
> 

-- 
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C  5EFA EF6A 7D2E 3E49 102A