2) There are builder.xml's that need some changes to get it running, i posted them as bugs (oalias has not-null field desciption, but null is set during import, same for some other builders) ?status?
I rejected this bug, see bugreport.
I will modify the oracle implementation TO SKIP CHECKING on null contrains then.
As i mentioned in my bugreport, the creation does set the value of description to null (maybe the name would be a nice work-around), furthermore there is some data in some applications that does not put a value in a field while this is required.
3) Last time i checked, there was an max = -1 failure, but RVM assured me that this was fixed now.
4) I didnt have time to create an implementation of storage, but this implementation should also work. (i hope to get an working storage implementation in the .1 version with full text search support)
Ok, so there is a full working version of the old database support class for oracle in cvs?
No, it has not-nullcontrains for some fields. I will remove this, to get oracle working. I want to mention that i do not fully agree with this descision.
After this modification i will have to check this again. I will try to get this working this evening, so it can be used on friday :D
