The hack i've done worked with inheritance. But since the old database layer doesnt work anymore (as far as i know), it can no longer be used. I posted an email about this on the list but i didnt get any response on it.Someone for Oracle?It is probably not required for the release to test it. If other databases work then oracle won't be a problem. There will be a version available in the future, because we need it for a project.
It's fair to say that currently Oracle is not supported. I know for a fact that Oracle support was broken in 1.6 (due to the new
inheritance code), and I would certainly not make any claims about
Oracle support in 1.7 unless explicitly tested.
I'm still working on a hsqldb implementation(in the storage) with views (same way as the oracle hack implemention works), after this oracle can be implemented the same way. I guess that this wont make it into 1.7, but it will be upwards compatible to the oracle hack.
I'd like to solve this problem in the storage layer by making the storage generic working with views, which means that:
- Creating a table will become creating a table and a view
- Inserting a record will become different
- Modifing a record will become different
- Deleting a record will become different
The code is not complex, but it has to be done and implemented.
I like to know what others think about this and where i / we should place the priorities (i have 2 weeks free starting from next monday). We could also make the decision to use oracle with duplicate values stored, but i never considerd this as an sollution.
