It's been proposed that it's finally time to drop support for some of the older versions of Oracle. Setting the new minimum version to 10.2 would mean that we could use Conditional Compilation rather than the current technique of special comment tags to selectively enable features depending on Oracle version. We could also remove a lot of the legacy code and use it as an opportunity to tidy up and refactor.
A new major version is the ideal time to introduce any breaking-changes that might otherwise not be compatible with the current version.
What other changes would people like to see?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometime ago I planned to start writing some unit tests to test utplsql - this fell by the way side, I hope to resurrect that. That might make it easier to start dropping the old versions of the software
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now that i think about it...
We could join the effort of testing utPLSQL with documenting it.
We could have example use cases (as simpe as possible).
Those examples should be part of testing suite for utPLSQL.
Executing those examples should be proving that particular pieces of utPLSQL are working.
This way we can kill two birds with one stone. Have a nice documentation by example Have a set of tests for utPLSQL
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sounds like a good idea to "refresh" the project and remove obsolete code.
Since current version is already supporting older Oracle versions, we could also start with Oracle 11g and forget about 10.
I wonder if Oracle shares the information about number of active licenses per Oracle version.
I'm not really a big fan of backward-compatibility. It usually brings lots of extra effort to project and makes some changes impossible to happen.
Getting rid of the burden of backward compatibility makes project lighter and allows getting easily up to speed with new features.
For older version of Oracle, older versions of utPLSQL are available...
What are your thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not particularly worried where we draw the line at the moment. There certainly is an argument for dropping 10 - it looks like it has been out of Extended Support for a couple of years (http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's been proposed that it's finally time to drop support for some of the older versions of Oracle. Setting the new minimum version to 10.2 would mean that we could use Conditional Compilation rather than the current technique of special comment tags to selectively enable features depending on Oracle version. We could also remove a lot of the legacy code and use it as an opportunity to tidy up and refactor.
A new major version is the ideal time to introduce any breaking-changes that might otherwise not be compatible with the current version.
What other changes would people like to see?
Sometime ago I planned to start writing some unit tests to test utplsql - this fell by the way side, I hope to resurrect that. That might make it easier to start dropping the old versions of the software
I like the idea of testing utPLSQL with utPLSQL :)
Now that i think about it...
We could join the effort of testing utPLSQL with documenting it.
We could have example use cases (as simpe as possible).
Those examples should be part of testing suite for utPLSQL.
Executing those examples should be proving that particular pieces of utPLSQL are working.
This way we can kill two birds with one stone.
Have a nice documentation by example
Have a set of tests for utPLSQL
Sounds like a good idea to "refresh" the project and remove obsolete code.
Since current version is already supporting older Oracle versions, we could also start with Oracle 11g and forget about 10.
I wonder if Oracle shares the information about number of active licenses per Oracle version.
I'm not really a big fan of backward-compatibility. It usually brings lots of extra effort to project and makes some changes impossible to happen.
Getting rid of the burden of backward compatibility makes project lighter and allows getting easily up to speed with new features.
For older version of Oracle, older versions of utPLSQL are available...
What are your thoughts?
I'm not particularly worried where we draw the line at the moment. There certainly is an argument for dropping 10 - it looks like it has been out of Extended Support for a couple of years (http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf)