|
|
|
|
| Index | Recent Threads | Unanswered Threads | Who's Online | User List | Help |
DataNucleus Forum
Development of DataNucleus
General Development
Thread: Most tests currently fail on Oracle?
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
jfrantzius
Advanced Member Germany Joined: Jun 18, 2004 Post Count: 407 Status: Offline |
Hi, when running the JUnit tests, lots of tests fail on Oracle because some autoassign id fields are used, e.g. [2006-01-04 23:12:30,150] ERROR RDBMSManager.java:248 - Failed initialising database. Exception : Class "org.jpox.samples.rate.Rate" has field "id" specified as using autoassign/id entity, yet the RDBMS in use doesnt support this feature javax.jdo.JDOFatalInternalException: Class "org.jpox.samples.rate.Rate" has field "id" specified as using autoassign/identity, yet the RDBMS in use doesnt support this feature at org.jpox.store.rdbms.table.ClassTable.initializePK(ClassTable.java:650) I'd guess this is not intended? Or is Oracle going to be removed from the list of supported databases ;) (In my opinion, it should deserve that already for calling itself "10g" in the year 2006, while it still does not support table names longer than 32 characters :-/ ) --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. |
||
|
|
andy
Expert UK Joined: Mar 13, 2004 Post Count: 5235 Status: Offline |
lots of tests fail on Oracle because some autoassign id fields are used, I'd guess this is not intended? Or is Oracle going to be removed from the list of supported databases ;) It's never been on my list of supported databases since I dont have it. If you look at the unit tests for other RDBMS that dont support autoassign (e.g Postgresql) you will find no problem at all. The unit tests should check if autoassign is supported and only run the test for that RDBMS. Its up to people with Oracle to sort it out  ---------------------------------------- Andy --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. ---------------------------------------- -Andy   |
||
|
|
jfrantzius
Advanced Member Germany Joined: Jun 18, 2004 Post Count: 407 Status: Offline |
The unit tests should check if autoassign is supported and only run the test for that RDBMS. Its up to people with Oracle to sort it out Then we'd ignore some tests for Oracle (can't count them right now). I wonder why autoassign is used anyway? If it's about testing autoassign, then there probably should be a dedicated test which we could lightheartedly ignore on Oracle? --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. |
||
|
|
andy
Expert UK Joined: Mar 13, 2004 Post Count: 5235 Status: Offline |
I wonder why autoassign is used anyway? If it's about testing autoassign, then there probably should be a dedicated test which we could lightheartedly ignore on Oracle? Because you can't just test "autoassign", since it impacts on other things. You have to test autoassign with other functionality ... inheritance, relationships, attachj/detach, everything else. Auto-assign is NOT used in that many tests, or at least shouldn't be. It is possible to use it with Postgresql with no issues so I dont see why you have so many things in Oracle causing problems - perhaps some misconfigured test setup ---------------------------------------- Andy --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. ---------------------------------------- -Andy |
||
|
|
jfrantzius
Advanced Member Germany Joined: Jun 18, 2004 Post Count: 407 Status: Offline |
I wonder why autoassign is used anyway? If it's about testing autoassign, then there probably should be a dedicated test which we could lightheartedly ignore on Oracle? Because you can't just test "autoassign", since it impacts on other things. You have to test autoassign with other functionality ... inheritance, relationships, attachj/detach, everything else. Auto-assign is NOT used in that many tests, or at least shouldn't be. It is possible to use it with Postgresql with no issues so I dont see why you have so many things in Oracle causing problems - perhaps some misconfigured test setup Well, Oracle simply doesn't have that feature, that's why there are so many problems with it :-( --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. |
||
|
|
andy
Expert UK Joined: Mar 13, 2004 Post Count: 5235 Status: Offline |
Well, Oracle simply doesn't have that feature, that's why there are so many problems with it :-( Please read my first post above. As I said, Postgresql simply <U>does not have that feature</U> either ... and the tests work. You have to work out why you have issues with Oracle because I cant. There is a DatabaseAdapter.supportsAutoIncrementFields or something. This is checked in the tests and RDBMS with it set to false (which is Oracle, or Postgresql) dont run those tests. There are only 2 sets of test samples using autoassign ... Currency/Rate, and the autoincrement package. ---------------------------------------- Andy --------------------------------------- This post has been recovered after a database corruption and might completely or partially lack replies. This thread had 5 replies before corruption. ---------------------------------------- -Andy |
||
|
|
|
|
Current timezone is GMT Mar 17, 2010 11:02:14 PM |
