Oystein Grovlen - Sun Norway wrote: > I was thinking of exisiting applications running against existing > databases vs new applications on a new database; not both existing and > new application against the same database. In other words, would it be > possible to turn it on automatically for new databases while new > versions against old databases will work as before?
What about existing applications creating databases? What about new applications running against existing databases? > I just realized that what I ask for is soft upgrade. In other words, do > we have to keep the old authorization as the default to provide for > backward compatibility? Could we not just require that old applications > run in soft upgrade mode if they do not want to deal with SQL > authorization? I don't think so. What if an existing application wants to use performance improvements in the new release, or be slightly modified to use JDBC 4.0 or updateable result sets? Dan.
